On Mon, Mar 13, 2017 at 10:58:29PM +0100, Kai Krakow wrote:
> Am Sat, 28 Jan 2017 15:50:38 -0500
> schrieb Matt McKinnon :
>
> > This same file system (which crashed again with the same errors) is
> > also giving this output during a metadata or data balance:
>
> This looks
Am Sat, 28 Jan 2017 15:50:38 -0500
schrieb Matt McKinnon :
> This same file system (which crashed again with the same errors) is
> also giving this output during a metadata or data balance:
This looks somewhat familiar to the err=-17 that I am experiencing when
using
I have an error on this file system I've had in the distant pass where
the mount would fail with a "file exists" error. Running a btrfs check
gives the following over and over again:
Found file extent holes:
start: 0, len: 290816
root 257 inode 28472371 errors 1000, some csum missing
This same file system (which crashed again with the same errors) is also
giving this output during a metadata or data balance:
Jan 27 19:42:47 my_machine kernel: [ 335.018123] BTRFS info (device
sda1): no csum found for inode 28472371 start 2191360
Jan 27 19:42:47 my_machine kernel: [
On Mon, Jan 23, 2017 at 03:03:55PM -0500, Matt McKinnon wrote:
> Wondering what to do about this error which says 'reboot needed'. Has
> happened a three times in the past week:
>
Well, I don't think btrfs's logic here is wrong, the following stack
shows that a nfs client has sent a second
On Mon, Jan 23, 2017 at 09:27:22PM +0100, Hans van Kranenburg wrote:
> On 01/23/2017 09:03 PM, Matt McKinnon wrote:
> > Wondering what to do about this error which says 'reboot needed'. Has
> > happened a three times in the past week:
> >
> > Jan 23 14:16:17 my_machine kernel: [ 2568.595648]
On 01/23/2017 09:27 PM, Hans van Kranenburg wrote:
> [... press send without rereading ...]
>
> Anyway, it seems to point to something that's going wrong with changes
> that are *not* on disk *yet*, and the crash is preventing ...
... whatever incorrect data this situation might result in from
On 01/23/2017 09:03 PM, Matt McKinnon wrote:
> Wondering what to do about this error which says 'reboot needed'. Has
> happened a three times in the past week:
>
> Jan 23 14:16:17 my_machine kernel: [ 2568.595648] BTRFS error (device
> sda1): err add delayed dir index item(index: 23810) into the
Wondering what to do about this error which says 'reboot needed'. Has
happened a three times in the past week:
Jan 23 14:16:17 my_machine kernel: [ 2568.595648] BTRFS error (device
sda1): err add delayed dir index item(index: 23810) into the deletion
tree of the delayed node(root id: 257,