On Jan 14, 2014, at 4:24 PM, Holger Brandsmeier <brandsme...@gmail.com> wrote:
> Dear Chris, > > as requested: > > # btrfs fi show > Label: none uuid: 267f069c-11da-4d2a-88fa-00cab4e28149 > Total devices 1 FS bytes used 12.68GiB > devid 1 size 29.82GiB used 24.27GiB path /dev/sdb1 > Label: none uuid: f6907d81-f46f-4911-8600-858e8b6bd1a0 > Total devices 1 FS bytes used 141.72GiB > devid 1 size 278.00GiB used 212.04GiB path /dev/sda5 > Btrfs v3.12 > > The problem makes `/dev/sda5`. I attached the output of `smartctl -x > /dev/sda5`. There are some reallocated sectors. dmesg reports [ 2023.770828] btrfs read error corrected: ino 1 off 605564928 (dev /dev/sda5 sector 1199128) That might be metadata on a bad sector that was fixed from duplicate metadata. This is single device Btrfs with default DUP metadata? > > # mount -o clear_cache /dev/sda5 data/ > mount: wrong fs type, bad option, bad superblock on /dev/sda5, > missing codepage or helper program, or other error > Hmm. So maybe the 1st superblock is no good. But it might be worth trying btrfs-zero-log first. It's possible the repair made this worse. https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg27613.html Chris Murphy -- 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
