Lakshmipathi.G posted on Mon, Oct 30, 2017 at 12:07 AM as excerpted: > Can you share these steps as simple bash script? Currently I'm running > few tests, I can check your script and share the results.
sure, but it is pretty trivial: device1=/dev/disk/by-id/XX1 device2=/dev/disk/by-id/XX2 device3=/dev/disk/by-id/XX3 mkfs.btrfs -L OfflineJ $device1 $device2 $device3 mount -t btrfs $device1 /mnt btrfs subvolume create /mnt/dataroot mkdir -p /media/OfflineJ umount /mnt mount -o subvol=/dataroot $device1 /media/OfflineJ > > The only thing I could think of is that the btrfs version that I used to > > mkfs > > was not up to date. Is there a way to determine which version was used to > > create the filesystem? > > > If I'm not wrong, i don't think we can get mkfs version from existing file > system layout. what was your kernel version? Not quite sure. Oldest: archlinux linux-lts as of 2017.06.08 Most likely: archlinux linux-lts as of 2017.10.18 It may be possible that I updated and created the fs without rebooting or reloading the kernel modules. But normally in that case any interaction, even mounting, just fails loudly. Duncan posted on Mon, Oct 30, 2017 at 12:09 AM as excerpted: > and I downclocked it a notch (from its rated pc3200 to 3000, IIRC). At Hmm, I did have a mild overclock on this system when I used it as a desktop but I thought I reverted it when I made it into a server. I'll double check this. > sometimes, but not always, trigger as well, but the most frequent symptom > really was checksum verification failures untarring tbz2s. I'll have to try and recreate this using my EXT4 system disk. Zak Kohler posted on Sun, Oct 29, 2017 at 9:57 PM as excerpted: > I'm running '$ sudo btrfs scrub start --offline --progress > /dev/disk/by-id/WD-XX3' one more time to just to make sure that I > wasn't reading something wrong. Well even stranger news on the fourth run: $ sudo btrfs scrub start --offline --progress /dev/disk/by-id/WD-XX3 Csum error: 175 # first run Csum error: 112 # second run... Csum error: 285 # third run... Csum error: 0 # fourth run Also can anyone confirm that the above --offline command checks the whole filesystem regardless which device is specified on the cli? > Only other think I can think to try is transferring those drives to > another system. I still need to try this also. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
