Re: read time tree block corruption detected

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

 



Nah, this 'corruption' hasn't affected anything other than not being
able to go to a newer kernel.  The system doesn't do anything
important.  I'll grab the logs, and clone an image of the drive so I
don't need to go single user RO mode to get dumps for devs when follow
up requests come in.

On Sun, Dec 29, 2019 at 3:11 PM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote:
>
> On Sun, Dec 29, 2019 at 3:36 PM Patrick Erley <pat-lkml@xxxxxxxxx> wrote:
> >
> > K.  Gotta roll a new initrd with btrfs 5.4, then will reboot into it
> > and grab logs of btrfs check (both iterations, against each of my
> > volumes).  Probably be a few hours, so don't expect another follow up
> > until tomorrow.  Thanks for chiming in.
> >
> > Would it be worth creating an image of the drive while I'm in single
> > user mode for faster analysis/iteration?
>
> Depends on the developer who replies. These days they usually just ask
> for selected dump-tree output. The image might be useful if you can't
> wait and want to blow away the file system and start over sooner than
> later.
>
>
>
> --
> Chris Murphy



[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