News for hackers. Stuff that matters.
Re:ntfs2btrfs: In-place conversion of NTFS filesystem to Btrfs by wtallis on Monday March 07, 2022 @06:05PM (#30594533)
This doesn't sound like a bug to me. It sounds like a refusal to fail silently.
Re:ntfs2btrfs: In-place conversion of NTFS filesystem to Btrfs by withinboredom on Monday March 07, 2022 @08:41PM (#30595533)
If you’re removing a device, it shouldn’t matter if the data is unreadable (that’s probably why it’s being removed, no?)
Re:ntfs2btrfs: In-place conversion of NTFS filesystem to Btrfs by wtallis on Monday March 07, 2022 @11:25PM (#30596432)
I interpreted "being able to read or reconstruct all data" as meaning that there must exist a good valid copy of each chunk of data somewhere in the array, but not necessarily on the device that you're trying to remove or replace. That interpretation matches my experience, which is that btrfs can correctly handle replacing a drive that is dead or dying. You should certainly expect errors if eg. both copies of a chunk in a RAID1 are lost/corrupted.
Re:ntfs2btrfs: In-place conversion of NTFS filesystem to Btrfs by michaelmrose on Tuesday March 08, 2022 @02:57AM (#30597572)
If you have a read error can you expect to recover the rest of the data?
Re:ntfs2btrfs: In-place conversion of NTFS filesystem to Btrfs by withinboredom on Tuesday March 08, 2022 @07:40AM (#30599231)
I’d hope so. Just because one bit is missing from a file, doesn’t mean the rest of the files are gone.