All of lore.kernel.org
 help / color / mirror / Atom feed
* btrfs receive started to fail constantly for a subvolume
@ 2021-02-13 15:06 Cerem Cem ASLAN
  2021-02-15 11:09 ` Filipe Manana
  0 siblings, 1 reply; 3+ messages in thread
From: Cerem Cem ASLAN @ 2021-02-13 15:06 UTC (permalink / raw)
  To: Btrfs BTRFS

Basically I'm using btrbk to create snapshots on main disk (MMM) and
send them 2 distinct disks (AAA and BBB). I have many nested
subvolumes (X, X/foo/Y, etc), so every distinct subvolume is
enumerated separately, like X.111, X.112, ..., X/foo/Y.111,
X/foo/Y.112, etc. Setup worked well for 100s of snapshots and backups
(send/receive) within the last 2 months.

Currently there is one offending subvolume that couldn't be sent to
disk AAA (say X.111). I tried to send it a couple of times even though
the huge size (230GB, takes 4 hour for every test) but there was no
success.

Error was like:

ERROR: ... sh: btrfs send -p
/mnt/MMM-root/snapshots/erik3/rootfs.20210213T0356 -c
/mnt/MMM-root/snapshots/erik3/rootfs.20210213T0414
/mnt/MMM-root/snapshots/erik3/home/ceremcem.20210213T0356 | mbuffer -v
1 | btrfs receive /mnt/AAA-root/snapshots/erik3/home/
ERROR: ... cannot open
/mnt/AAA-root/snapshots/erik3/home/ceremcem.20210213T0356/o10179316-137012-0:
No such file or directory

I tried to issue `btrfs send
/mnt/MMM-root/snapshots/erik3/home/ceremcem.20210213T0356 | pv >
/dev/null` to see if there is anything wrong with the source snapshot,
but it succeeded.

Skipping the other intermediate attempts, I tried to remove every
snapshot in AAA, BBB, reformat AAA and BBB with mkfs.btrfs, deleted
all snapshots and created a new set on MMM, tried to send everything
from scratch. It failed with nearly the same error (can't remember
now) on the same subvolume
(/mnt/MMM-root/snapshots/erik3/home/ceremcem.XXX).

I ran a btrfs scrub on /mnt/MMM-root and there were no errors.

Why do I keep getting this error?

uname -a
Linux erik3 5.9.0-0.bpo.5-amd64 #1 SMP Debian 5.9.15-1~bpo10+1
(2020-12-31) x86_64 GNU/Linux

btrfs-progs v5.10

^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: btrfs receive started to fail constantly for a subvolume
  2021-02-13 15:06 btrfs receive started to fail constantly for a subvolume Cerem Cem ASLAN
@ 2021-02-15 11:09 ` Filipe Manana
  2021-02-23 14:59   ` Cerem Cem ASLAN
  0 siblings, 1 reply; 3+ messages in thread
From: Filipe Manana @ 2021-02-15 11:09 UTC (permalink / raw)
  To: Cerem Cem ASLAN; +Cc: Btrfs BTRFS

On Sat, Feb 13, 2021 at 3:09 PM Cerem Cem ASLAN <ceremcem@ceremcem.net> wrote:
>
> Basically I'm using btrbk to create snapshots on main disk (MMM) and
> send them 2 distinct disks (AAA and BBB). I have many nested
> subvolumes (X, X/foo/Y, etc), so every distinct subvolume is
> enumerated separately, like X.111, X.112, ..., X/foo/Y.111,
> X/foo/Y.112, etc. Setup worked well for 100s of snapshots and backups
> (send/receive) within the last 2 months.
>
> Currently there is one offending subvolume that couldn't be sent to
> disk AAA (say X.111). I tried to send it a couple of times even though
> the huge size (230GB, takes 4 hour for every test) but there was no
> success.
>
> Error was like:
>
> ERROR: ... sh: btrfs send -p
> /mnt/MMM-root/snapshots/erik3/rootfs.20210213T0356 -c
> /mnt/MMM-root/snapshots/erik3/rootfs.20210213T0414
> /mnt/MMM-root/snapshots/erik3/home/ceremcem.20210213T0356 | mbuffer -v
> 1 | btrfs receive /mnt/AAA-root/snapshots/erik3/home/
> ERROR: ... cannot open
> /mnt/AAA-root/snapshots/erik3/home/ceremcem.20210213T0356/o10179316-137012-0:
> No such file or directory
>
> I tried to issue `btrfs send
> /mnt/MMM-root/snapshots/erik3/home/ceremcem.20210213T0356 | pv >
> /dev/null` to see if there is anything wrong with the source snapshot,
> but it succeeded.
>
> Skipping the other intermediate attempts, I tried to remove every
> snapshot in AAA, BBB, reformat AAA and BBB with mkfs.btrfs, deleted
> all snapshots and created a new set on MMM, tried to send everything
> from scratch. It failed with nearly the same error (can't remember
> now) on the same subvolume
> (/mnt/MMM-root/snapshots/erik3/home/ceremcem.XXX).
>
> I ran a btrfs scrub on /mnt/MMM-root and there were no errors.
>
> Why do I keep getting this error?
>
> uname -a
> Linux erik3 5.9.0-0.bpo.5-amd64 #1 SMP Debian 5.9.15-1~bpo10+1

Assuming this is a 5.9.0 vanilla kernel, or something close enough,
then you are missing some bug fixes that are likely to solve this:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0b3f407e6728d990ae1630a02c7b952c21c288d3
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9c2b4e0347067396ceb3ae929d6888c81d610259
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=98272bb77bf4cc20ed1ffca89832d713e70ebf09

These are all in recent stable kernels (the versions listed in kernel.org).

> (2020-12-31) x86_64 GNU/Linux
>
> btrfs-progs v5.10



-- 
Filipe David Manana,

“Whether you think you can, or you think you can't — you're right.”

^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: btrfs receive started to fail constantly for a subvolume
  2021-02-15 11:09 ` Filipe Manana
@ 2021-02-23 14:59   ` Cerem Cem ASLAN
  0 siblings, 0 replies; 3+ messages in thread
From: Cerem Cem ASLAN @ 2021-02-23 14:59 UTC (permalink / raw)
  To: fdmanana; +Cc: Btrfs BTRFS

Thanks for the info. I upgraded the kernel to 5.10.0-0.bpo.3-amd64.

Filipe Manana <fdmanana@gmail.com>, 15 Şub 2021 Pzt, 14:09 tarihinde şunu yazdı:
>
> On Sat, Feb 13, 2021 at 3:09 PM Cerem Cem ASLAN <ceremcem@ceremcem.net> wrote:
> >
> > Basically I'm using btrbk to create snapshots on main disk (MMM) and
> > send them 2 distinct disks (AAA and BBB). I have many nested
> > subvolumes (X, X/foo/Y, etc), so every distinct subvolume is
> > enumerated separately, like X.111, X.112, ..., X/foo/Y.111,
> > X/foo/Y.112, etc. Setup worked well for 100s of snapshots and backups
> > (send/receive) within the last 2 months.
> >
> > Currently there is one offending subvolume that couldn't be sent to
> > disk AAA (say X.111). I tried to send it a couple of times even though
> > the huge size (230GB, takes 4 hour for every test) but there was no
> > success.
> >
> > Error was like:
> >
> > ERROR: ... sh: btrfs send -p
> > /mnt/MMM-root/snapshots/erik3/rootfs.20210213T0356 -c
> > /mnt/MMM-root/snapshots/erik3/rootfs.20210213T0414
> > /mnt/MMM-root/snapshots/erik3/home/ceremcem.20210213T0356 | mbuffer -v
> > 1 | btrfs receive /mnt/AAA-root/snapshots/erik3/home/
> > ERROR: ... cannot open
> > /mnt/AAA-root/snapshots/erik3/home/ceremcem.20210213T0356/o10179316-137012-0:
> > No such file or directory
> >
> > I tried to issue `btrfs send
> > /mnt/MMM-root/snapshots/erik3/home/ceremcem.20210213T0356 | pv >
> > /dev/null` to see if there is anything wrong with the source snapshot,
> > but it succeeded.
> >
> > Skipping the other intermediate attempts, I tried to remove every
> > snapshot in AAA, BBB, reformat AAA and BBB with mkfs.btrfs, deleted
> > all snapshots and created a new set on MMM, tried to send everything
> > from scratch. It failed with nearly the same error (can't remember
> > now) on the same subvolume
> > (/mnt/MMM-root/snapshots/erik3/home/ceremcem.XXX).
> >
> > I ran a btrfs scrub on /mnt/MMM-root and there were no errors.
> >
> > Why do I keep getting this error?
> >
> > uname -a
> > Linux erik3 5.9.0-0.bpo.5-amd64 #1 SMP Debian 5.9.15-1~bpo10+1
>
> Assuming this is a 5.9.0 vanilla kernel, or something close enough,
> then you are missing some bug fixes that are likely to solve this:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0b3f407e6728d990ae1630a02c7b952c21c288d3
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9c2b4e0347067396ceb3ae929d6888c81d610259
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=98272bb77bf4cc20ed1ffca89832d713e70ebf09
>
> These are all in recent stable kernels (the versions listed in kernel.org).
>
> > (2020-12-31) x86_64 GNU/Linux
> >
> > btrfs-progs v5.10
>
>
>
> --
> Filipe David Manana,
>
> “Whether you think you can, or you think you can't — you're right.”

^ permalink raw reply	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-02-23 15:00 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-02-13 15:06 btrfs receive started to fail constantly for a subvolume Cerem Cem ASLAN
2021-02-15 11:09 ` Filipe Manana
2021-02-23 14:59   ` Cerem Cem ASLAN

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.