btrfs send and kernel 3.17

DISCUSSION David Arendt 2 participants 5 messages Oct 6, 2014 Btrfs file system

lore

Share & tools

lore

David Arendt

author

2014-10-06 19:02 UTC #0 lore raw

Hi,

After upgrading to kernel 3.17 btrfs send has stopped working.

ERROR: send ioctl failed with -5: Input/output error

The following message is printed by kernel:

[75322.782197] BTRFS error (device sda2): did not find backref in

send_root. inode=461, offset=0, disk_byte=1094713344 found extent=1094713344

btrfs inspect-internal inode-resolve -v 461 /u00/root.snapshot returns:

/var/log/emerge-fetch.log

After removing this file, the error moves on to another file.

btrfs scrub output:

scrub status for bc31b068-2c36-4ff2-ac5c-7ce55af5371d

    scrub started at Mon Oct  6 19:49:25 2014 and finished after 1748

seconds
total bytes scrubbed: 94.21GiB with 0 errors

Other then the btrfs send problem, the filesystem works normally.

Is this a bug in btrfs-send or is my filesystem corrupted and should be restored from backup ?

Please tell me if I can do anything else to help debugging this issue.

Thanks in advance,
David Arendt

Chris Mason

2014-10-06 19:06 UTC #1 lore raw

Quoted 24 lines · David Arendt

Hi,
After upgrading to kernel 3.17 btrfs send has stopped working.
ERROR: send ioctl failed with -5: Input/output error
The following message is printed by kernel:
[75322.782197] BTRFS error (device sda2): did not find backref in
send_root. inode=461, offset=0, disk_byte=1094713344 found extent=1094713344
btrfs inspect-internal inode-resolve -v 461 /u00/root.snapshot returns:
/var/log/emerge-fetch.log
After removing this file, the error moves on to another file.
btrfs scrub output:
scrub status for bc31b068-2c36-4ff2-ac5c-7ce55af5371d
    scrub started at Mon Oct  6 19:49:25 2014 and finished after 1748
seconds
total bytes scrubbed: 94.21GiB with 0 errors

Quoted 6 lines

Other then the btrfs send problem, the filesystem works normally.
Is this a bug in btrfs-send or is my filesystem corrupted and should be restored from backup ?
Please tell me if I can do anything else to help debugging this issue.

Which kernel did you upgrade from? I don't think we have changes in 3.17 that should impact this.

Is merge-fetch.log just a simple append-only log file?

-chris

David Arendt

author

2014-10-06 19:48 UTC #2 lore raw

I have upgraded from kernel 3.16.3.

emerge-fetch.log is a simple append-only log file. Other files having the problems after deleting them one by one have been emerge.log, mysql.log, freshclam.log and main.cvd from clamav. At this one, I stopped deleting.

Quoted 46 lines · Chris Mason

Quoted 25 lines · David Arendt
Hi,
After upgrading to kernel 3.17 btrfs send has stopped working.
ERROR: send ioctl failed with -5: Input/output error
The following message is printed by kernel:
[75322.782197] BTRFS error (device sda2): did not find backref in
send_root. inode=461, offset=0, disk_byte=1094713344 found extent=1094713344
btrfs inspect-internal inode-resolve -v 461 /u00/root.snapshot returns:
/var/log/emerge-fetch.log
After removing this file, the error moves on to another file.
btrfs scrub output:
scrub status for bc31b068-2c36-4ff2-ac5c-7ce55af5371d
    scrub started at Mon Oct  6 19:49:25 2014 and finished after 1748
seconds
total bytes scrubbed: 94.21GiB with 0 errors
Quoted 6 lines
Other then the btrfs send problem, the filesystem works normally.
Is this a bug in btrfs-send or is my filesystem corrupted and should be restored from backup ?
Please tell me if I can do anything else to help debugging this issue.
Which kernel did you upgrade from? I don't think we have changes in 3.17 that should impact this.
Is merge-fetch.log just a simple append-only log file?
-chris
Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

David Arendt

author

2014-10-06 21:01 UTC #3 lore raw

In reply to Chris Mason

I just tried downgrading to 3.16.3 again. In 3.16.3 btrfs send is working without any problem. Afterwards I upgraded again to 3.17 and the problem reappeared. So the problem seems to be kernel version related.

Quoted 46 lines · Chris Mason

Quoted 25 lines · David Arendt
Hi,
After upgrading to kernel 3.17 btrfs send has stopped working.
ERROR: send ioctl failed with -5: Input/output error
The following message is printed by kernel:
[75322.782197] BTRFS error (device sda2): did not find backref in
send_root. inode=461, offset=0, disk_byte=1094713344 found extent=1094713344
btrfs inspect-internal inode-resolve -v 461 /u00/root.snapshot returns:
/var/log/emerge-fetch.log
After removing this file, the error moves on to another file.
btrfs scrub output:
scrub status for bc31b068-2c36-4ff2-ac5c-7ce55af5371d
    scrub started at Mon Oct  6 19:49:25 2014 and finished after 1748
seconds
total bytes scrubbed: 94.21GiB with 0 errors
Quoted 6 lines
Other then the btrfs send problem, the filesystem works normally.
Is this a bug in btrfs-send or is my filesystem corrupted and should be restored from backup ?
Please tell me if I can do anything else to help debugging this issue.
Which kernel did you upgrade from? I don't think we have changes in 3.17 that should impact this.
Is merge-fetch.log just a simple append-only log file?
-chris
Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Chris Mason

2014-10-06 22:22 UTC #4 lore raw

Quoted 3 lines · David Arendt

I just tried downgrading to 3.16.3 again. In 3.16.3 btrfs send is working without any problem. Afterwards I upgraded again to 3.17 and the problem reappeared. So the problem seems to be kernel version related.

[ backref errors during btrfs-send ]

Ok then, our list of suspects is pretty short. Can you easily build test kernels?

I'd like to try reverting this commit:

51f395ad4058883e4273b02fdebe98072dbdc0d2

-chris