Re: RAID1 filesystem not mounting

2019-02-02 Thread Bernhard K
On 02.02.2019 05:28 Alan Hardman wrote: > Also, "btrfs restore -Dv /dev/sdb /tmp" outputs some of the files on the > filesystem but not all of them. I'm not sure if this is limited to the files > on that physical disk, or if there's a bigger issue with the filesystem. I'm > not sure what the bes

Re: RAID1 filesystem not mounting

2019-02-02 Thread Hugo Mills
On Fri, Feb 01, 2019 at 11:28:27PM -0500, Alan Hardman wrote: > I have a Btrfs filesystem using 6 partitionless disks in RAID1 that's failing > to mount. I've tried the common recommended safe check options, but I haven't > gotten the disk to mount at all, even with -o ro,recovery. If necessary,

Re: btrfs as / filesystem in RAID1

2019-02-02 Thread Chris Murphy
On Fri, Feb 1, 2019 at 3:28 AM Stefan K wrote: > > Hello, > > I've installed my Debian Stretch to have / on btrfs with raid1 on 2 SSDs. > Today I want test if it works, it works fine until the server is running and > the SSD get broken and I can change this, but it looks like that it does not >

Re: RAID1 filesystem not mounting

2019-02-02 Thread Chris Murphy
On Fri, Feb 1, 2019 at 9:28 PM Alan Hardman wrote: > > I have a Btrfs filesystem using 6 partitionless disks in RAID1 that's failing > to mount. I've tried the common recommended safe check options, but I haven't > gotten the disk to mount at all, even with -o ro,recovery. Try '-o ro,degraded,n

Re: RAID1 filesystem not mounting

2019-02-02 Thread Chris Murphy
On Sat, Feb 2, 2019 at 5:02 AM Hugo Mills wrote: > > On Fri, Feb 01, 2019 at 11:28:27PM -0500, Alan Hardman wrote: > > I have a Btrfs filesystem using 6 partitionless disks in RAID1 that's > > failing to mount. I've tried the common recommended safe check options, but > > I haven't gotten the di

Re: RAID1 filesystem not mounting

2019-02-02 Thread Alan Hardman
Thanks for the quick response, Chris and Hugo! After some testing, there *was* a RAM issue that has now been resolved, so that should prevent it from being a factor going forward, but could definitely have been related. The high number of lifetime errors for the filesystem is expected, and isn'