Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is this a fault? #47

Closed
daiaji opened this issue May 31, 2022 · 3 comments
Closed

Is this a fault? #47

daiaji opened this issue May 31, 2022 · 3 comments

Comments

@daiaji
Copy link

daiaji commented May 31, 2022

sudo ntfs2btrfs  /dev/disk/by-id/nvme-P6F3840_SE19C11P7050835-part1 
Using Zstd compression.
Using CRC32C for checksums.
Processing inode 596892 / 596892 (100.0%)
Mapped 220431 inodes directly.
Rewrote 107690 inodes.
Inlined 93062 inodes.
Updating directory sizes
Calculating checksums 9713735 / 9713735 (100.0%)
/usr/include/c++/12.1.0/bits/stl_vector.h:1123: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = unsigned char; _Alloc = default_init_allocator<unsigned char>; reference = unsigned char&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.
zsh: IOT instruction  sudo ntfs2btrfs /dev/disk/by-id/nvme-P6F3840_SE19C11P7050835-part1
@jarrard
Copy link

jarrard commented Jul 16, 2022

/usr/include/c++/12.1.0/bits/stl_vector.h:1123: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator [with _Tp = unsigned char; _Alloc = default_init_allocator; reference = unsigned char&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.
Aborted

I get the above. I really don't know why the fix isn't put into master.
Guess this project is a dead end if it isn't going to be maintained to at least work without needing users to go in and patch the source themselves!

@maharmstone
Copy link
Owner

I'm sick to the back teeth of this "bug". It's not even a bug, it's a false positive caused by one of the distros having the brilliant idea to compile things with debug assertions turned on. And it is already fixed, or rather worked around, in master.

@jarrard
Copy link

jarrard commented Jul 16, 2022

Ok fair enough. I couldn't get ntfs to btrfs to work for me either way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants