Re: btrfs partition fails to mount after power outage

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Aug 23, 2016 at 9:51 AM, Malte Westerhoff
<MWesterhoff@xxxxxxxxxxxxxxxxx> wrote:
>     >>     btrfs-show-super -fa /d/dev/mapper/VGBIGRAID6-DATA1
>
>>    Where is this output?
>
> I had attached it as a separate file. Here it is again:

Sorry, missed that there was an attachment.



> backup_roots[4]:
>         backup 0:
>                 backup_tree_root:       3421559472128   gen: 52059      level: 1
>                 backup_chunk_root:      20971520        gen: 52005      level: 1
>                 backup_extent_root:     3421770170368   gen: 52059      level: 3
>                 backup_fs_root:         29556736        gen: 6  level: 0
>                 backup_dev_root:        7304828502016   gen: 52059      level: 1
>                 backup_csum_root:       7315970588672   gen: 52059      level: 3
>                 backup_total_bytes:     17592186044416
>                 backup_bytes_used:      7386753196032
>                 backup_num_devices:     1
>
>         backup 1:
>                 backup_tree_root:       7442297503744   gen: 52056      level: 1
>                 backup_chunk_root:      20971520        gen: 52005      level: 1
>                 backup_extent_root:     7442294161408   gen: 52056      level: 3
>                 backup_fs_root:         29556736        gen: 6  level: 0
>                 backup_dev_root:        7254075654144   gen: 52005      level: 1
>                 backup_csum_root:       7442298175488   gen: 52056      level: 3
>                 backup_total_bytes:     17592186044416
>                 backup_bytes_used:      7386753163264
>                 backup_num_devices:     1
>
>         backup 2:
>                 backup_tree_root:       7442289229824   gen: 52057      level: 1
>                 backup_chunk_root:      20971520        gen: 52005      level: 1
>                 backup_extent_root:     7442283692032   gen: 52057      level: 3
>                 backup_fs_root:         29556736        gen: 6  level: 0
>                 backup_dev_root:        7254075654144   gen: 52005      level: 1
>                 backup_csum_root:       7442294063104   gen: 52057      level: 3
>                 backup_total_bytes:     17592186044416
>                 backup_bytes_used:      7386753179648
>                 backup_num_devices:     1
>
>         backup 3:
>                 backup_tree_root:       7442297503744   gen: 52058      level: 1
>                 backup_chunk_root:      20971520        gen: 52005      level: 1
>                 backup_extent_root:     7442284920832   gen: 52058      level: 3
>                 backup_fs_root:         29556736        gen: 6  level: 0
>                 backup_dev_root:        7254075654144   gen: 52005      level: 1
>                 backup_csum_root:       7442299355136   gen: 52058      level: 3
>                 backup_total_bytes:     17592186044416
>                 backup_bytes_used:      7386753179648
>                 backup_num_devices:     1


Uhhhh, is anyone else having a WTF moment? Why is the backup_fs_root
generation 6 on all of these backup roots? Doesn't that seem really
unlikely? On all of my filesystems, the fs_root has a lower
generation, but isn't separated by this many generations.

What do you get for:

btrfs-debug-tree -b 29556736 /dev/mapper/VGBIGRAID6-DATA1





-- 
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux