Open
Description
after experiencing similar symptoms to this issue #147 (comment) i was asked to open a new issue, so here we are
btrfs-progs v6.12
linux 6.12.4
...to be honest, im not sure my filesystem qualifies as "fine"; here is what btrfs check reported:
Opening filesystem to check...
Checking filesystem on <device>
UUID: <uuid>
[1/8] checking log skipped (none written)
[2/8] checking root items
[3/8] checking extents
[4/8] checking free space tree
[5/8] checking fs roots
root 5 inode 11793850 errors 2000, link count wrong
root 261 inode 11793850 errors 2000, link count wrong
root 262 inode 11793850 errors 2000, link count wrong
root 263 inode 11793850 errors 2000, link count wrong
ERROR: errors found in fs roots
found 3956634472448 bytes used, error(s) found
total csum bytes: 3854331828
total tree bytes: 9798680576
total fs tree bytes: 4650385408
total extent tree bytes: 816889856
btree space waste bytes: 1310094370
file data blocks allocated: 8986344386560
referenced 4395424018432
$ btrfs send <path/to/snapshot> | btrfs receive --dump > stream.dump
At subvol </absolute/path/to/snapshot>
ERROR: send ioctl failed with -2: No such file or directory
ERROR: unexpected EOF in stream
ERROR: failed to dump the send stream: Invalid argument
$ tail -20 stream.dump
utimes ./2024-12-13/o12028470-88279-0/git_help~20220720-190009.md atime=2022-07-03T12:59:18-0700 mtime=2022-07-03T12:59:18-0700 ctime=2022-07-20T19:00:09-0700
mkdir ./2024-12-13/o11793848-76593-0
rename ./2024-12-13/o11793848-76593-0 dest=./2024-12-13/$RECYCLE.BIN
utimes ./2024-12-13/.yay/rpmdevtools/.git/refs/heads atime=2024-11-20T18:47:07-0800 mtime=2022-06-27T14:04:45-0700 ctime=2022-06-27T14:04:45-0700
set_xattr ./2024-12-13/$RECYCLE.BIN name=security.NTACL<byte sequence removed> len=180
set_xattr ./2024-12-13/$RECYCLE.BIN name=user.DOSATTRIB 0x16 len=4
chown ./2024-12-13/$RECYCLE.BIN gid=100 uid=0
chmod ./2024-12-13/$RECYCLE.BIN mode=755
utimes ./2024-12-13/.yay/rpmdevtools/.git/logs atime=2024-11-20T18:47:07-0800 mtime=2022-06-27T14:04:42-0700 ctime=2022-06-27T14:04:42-0700
mkdir ./2024-12-13/o11793849-76593-0
rename ./2024-12-13/o11793849-76593-0 dest=./2024-12-13/$RECYCLE.BIN/S-1-5-21-2511366946-130215246-2013100535-1001
set_xattr ./2024-12-13/$RECYCLE.BIN/S-1-5-21-2511366946-130215246-2013100535-1001 name=security.NTACL <byte sequence removed> len=192
set_xattr ./2024-12-13/$RECYCLE.BIN/S-1-5-21-2511366946-130215246-2013100535-1001 name=user.DOSATTRIB 0x16 len=4
chown ./2024-12-13/$RECYCLE.BIN/S-1-5-21-2511366946-130215246-2013100535-1001 gid=100 uid=65534
chmod ./2024-12-13/$RECYCLE.BIN/S-1-5-21-2511366946-130215246-2013100535-1001 mode=755
utimes ./2024-12-13/.yay/rpmdevtools/.git/logs/refs atime=2024-11-20T18:47:07-0800 mtime=2022-06-27T14:04:42-0700 ctime=2022-06-27T14:04:42-0700
mkdir ./2024-12-13/o11793850-76593-0
set_xattr ./2024-12-13/o11793850-76593-0 name=security.NTACL <byte sequence removed> len=192
chown ./2024-12-13/o11793850-76593-0 gid=100 uid=65534
chmod ./2024-12-13/o11793850-76593-0 mode=755
after seeing the error seemingly occurred close to when processing the corrupt $RECYCLE.BIN directory (context #147 (comment)), my feeling is this is just due to filesystem corruption and probably not a fruitful report, but for posterity at the very least i figured i may as well post it. im happy to try any tests if there are any suggestions! (my data is safely on a new filesystem now), or if you just feel inclined to close this that works too.