Re: [4.7.2] btrfs_run_delayed_refs:2963: errno=-17 Object already exists

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



(Resend with the log compressed this time.)

On Friday 17 February 2017 09:19:15 Kai Krakow wrote:
> Am Tue, 14 Feb 2017 13:52:48 +0100
>
> schrieb Marc Joliet <marcec@xxxxxx>:
> > Hi again,
> >
> > so, it seems that I've solved the problem:  After having to
> > umount/mount the FS several times to get btrfs-cleaner to finish, I
> > thought of the "failed to load free space [...], rebuilding it now"
> > type errors and decided to try the clear_cache mount option.  Since
> > then, my home server has been running its backups regularly again.
> > Furthermore, I was able back up my desktop again via send/recv (the
> > rsync based backup is still running, but I expect it to succeed).
> > The kernel log has also stayed clean.

*sigh*

It was working fine... until the 26th (so almost 2 weeks without incident).
Now the error keeps occurring, and the clear_cache mount option stopped
helping.  Just out of curiosity, I used "clear_cache,space_cache=v2", which
also didn't help.  I've attached the full log, in case it's in any way useful.

This is all with:

% uname -a
Linux diefledermaus 4.9.12-gentoo #1 SMP Fri Feb 24 20:09:28 CET 2017 x86_64
Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz GenuineIntel GNU/Linux
% /sbin/btrfs --version
btrfs-progs v4.9

> > Kai, I'd be curious whether clear_cache will help in your case, too,
> > if you haven't tried it already.
>
> The FS in question has been rebuilt from scratch. AFAIR it wasn't even
> mountable back then, or at it froze the system short after mounting.
>
> I needed the system back in usable state, so I had to recreate and
> restore the system.

I think I'm at that point now myself, unless anybody has any other ideas.

What I *am* going to do before giving up and reformatting is create an image.
I found out that using the -w option to btrfs-image keeps it from segfaulting,
so I guess the underlying problem has to do with the extent tree?  However,
the image is... pretty damn big (8.6 GB by now, *after* compressing with "xz
-9"), and it's not even finished yet.  So, under the assumption that the image
could be useful to somebody, I would welcome any suggestions for where to
upload such an image once it's done.

> Next time, if it happens again (finger crossed it does not), I'll give
> it a try.

Yeah, I hope it doesn't come back, either, for either of us.

Greetings
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup

<<attachment: dmesg_since_20170226.log.zip>>

Attachment: signature.asc
Description: This is a digitally signed message part.


[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux