RE: raid6 file system in a bad state

2016-10-17 Thread Jason D. Michaelson
at the moment. Again, thanks for your help. > -Original Message- > From: ch...@colorremedies.com [mailto:ch...@colorremedies.com] On > Behalf Of Chris Murphy > Sent: Friday, October 14, 2016 4:55 PM > To: Chris Murphy > Cc: Jason D. Michaelson; Btrfs BTRFS > Subject: Re: raid6

Re: raid6 file system in a bad state

2016-10-14 Thread Chris Murphy
This may be relevant and is pretty terrible. http://www.spinics.net/lists/linux-btrfs/msg59741.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

Re: raid6 file system in a bad state

2016-10-12 Thread Chris Murphy
On Wed, Oct 12, 2016 at 11:59 AM, Jason D. Michaelson wrote: > With the bad disc in place: > > root@castor:~/btrfs-progs# ./btrfs restore -t 4844272943104 -D /dev/sda > /dev/null > parent transid verify failed on 4844272943104 wanted 161562 found 161476 > parent

RE: raid6 file system in a bad state

2016-10-12 Thread Jason D. Michaelson
> -Original Message- > From: ch...@colorremedies.com [mailto:ch...@colorremedies.com] On > Behalf Of Chris Murphy > Sent: Tuesday, October 11, 2016 3:38 PM > To: Jason D. Michaelson; Btrfs BTRFS > Cc: Chris Murphy > Subject: Re: raid6 file system in a bad stat

Re: raid6 file system in a bad state

2016-10-11 Thread Chris Murphy
ber 11, 2016 12:41 PM >> To: Jason D. Michaelson >> Cc: Chris Murphy; Btrfs BTRFS >> Subject: Re: raid6 file system in a bad state >> >> On Tue, Oct 11, 2016 at 10:10 AM, Jason D. Michaelson >> <jasond

Re: raid6 file system in a bad state

2016-10-11 Thread Chris Murphy
On Tue, Oct 11, 2016 at 10:10 AM, Jason D. Michaelson wrote: > superblock: bytenr=65536, device=/dev/sda > - > generation 161562 > root5752616386560 > superblock: bytenr=65536,

RE: raid6 file system in a bad state

2016-10-11 Thread Jason D. Michaelson
> > > Bad superblocks can't be a good thing and would only cause confusion. > I'd think that a known bad superblock would be ignored at mount time > and even by btrfs-find-root, or maybe even replaced like any other kind > of known bad metadata where good copies are available. > >

Re: raid6 file system in a bad state

2016-10-11 Thread Chris Murphy
On Tue, Oct 11, 2016 at 9:52 AM, Jason D. Michaelson wrote: >> btrfs rescue super-recover -v > > root@castor:~/logs# btrfs rescue super-recover -v /dev/sda > All Devices: > Device: id = 2, name = /dev/sdh > Device: id = 3, name = /dev/sdd >

RE: raid6 file system in a bad state

2016-10-11 Thread Jason D. Michaelson
> -Original Message- > From: ch...@colorremedies.com [mailto:ch...@colorremedies.com] On > Behalf Of Chris Murphy > Sent: Monday, October 10, 2016 11:23 PM > To: Jason D. Michaelson > Cc: Chris Murphy; Btrfs BTRFS > Subject: Re: raid6 file system in a bad state

Re: raid6 file system in a bad state

2016-10-10 Thread Chris Murphy
What do you get for btrfs-find-root btrfs rescue super-recover -v It shouldn't matter which dev you pick, unless it face plants, then try another. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo

Re: raid6 file system in a bad state

2016-10-10 Thread Chris Murphy
On Mon, Oct 10, 2016 at 10:04 AM, Jason D. Michaelson wrote: > One of the disks had a write problem, unbeknownst to me, which caused the > entire pool and its subvolumes to remount read only. Can you be more specific about the write problem? What are the messages