Re: Kernel crash on mount after SMR disk trouble

2016-06-11 Thread Jukka Larja
11.6.2016, 19.30, Chris Murphy kirjoitti: On Sat, Jun 11, 2016 at 6:40 AM, Jukka Larja wrote: 11.6.2016, 15.30, Chris Murphy kirjoitti: On Fri, Jun 10, 2016 at 9:11 PM, Jukka Larja wrote: I understand that usebackuproot requires kernel

Re: Kernel crash on mount after SMR disk trouble

2016-06-11 Thread Chris Murphy
On Sat, Jun 11, 2016 at 6:40 AM, Jukka Larja wrote: > 11.6.2016, 15.30, Chris Murphy kirjoitti: > >> On Fri, Jun 10, 2016 at 9:11 PM, Jukka Larja >> wrote: >> >>> I understand that usebackuproot requires kernel >= 4.6. I probably won't >>> be

Re: Kernel crash on mount after SMR disk trouble

2016-06-11 Thread Jukka Larja
11.6.2016, 15.30, Chris Murphy kirjoitti: On Fri, Jun 10, 2016 at 9:11 PM, Jukka Larja wrote: I understand that usebackuproot requires kernel >= 4.6. I probably won't be installing a custom kernel, but if I still have the array in its current state when 4.6 becomes

Re: Kernel crash on mount after SMR disk trouble

2016-06-11 Thread Chris Murphy
On Fri, Jun 10, 2016 at 9:11 PM, Jukka Larja wrote: > I understand that usebackuproot requires kernel >= 4.6. I probably won't be > installing a custom kernel, but if I still have the array in its current > state when 4.6 becomes available in Debian Stretch, I'll give

Re: Kernel crash on mount after SMR disk trouble

2016-06-10 Thread Jukka Larja
10.6.2016, 23.20, Henk Slager kirjoitti: On Sat, May 14, 2016 at 10:19 AM, Jukka Larja wrote: In short: I added two 8TB Seagate Archive SMR disk to btrfs pool and tried to delete one of the old disks. After some errors I ended up with file system that can be mounted

Re: Kernel crash on mount after SMR disk trouble

2016-06-10 Thread Henk Slager
On Sat, May 14, 2016 at 10:19 AM, Jukka Larja wrote: > In short: > > I added two 8TB Seagate Archive SMR disk to btrfs pool and tried to delete > one of the old disks. After some errors I ended up with file system that can > be mounted read-only, but crashes the kernel

Kernel crash on mount after SMR disk trouble

2016-05-14 Thread Jukka Larja
In short: I added two 8TB Seagate Archive SMR disk to btrfs pool and tried to delete one of the old disks. After some errors I ended up with file system that can be mounted read-only, but crashes the kernel if mounted normally. Tried btrfs check --repair (which noted that space cache needs to