From: Andrej Podzimek <andrej@podzimek.org>
To: linux-btrfs@vger.kernel.org
Subject: Errors during defragmentation
Date: Mon, 29 Nov 2010 22:02:56 +0100 [thread overview]
Message-ID: <4CF41500.8000804@podzimek.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]
Hello,
I decided to test the 'defragment' feature on my system (after a huge number of system updates and prelinking):
find /bin /sbin /lib /usr/lib /usr/bin /usr/sbin -type d -exec btrfs filesystem defragment '{}' '+'
I have already defragmented a couple of (very large) directories with no errors at all, so this was expected to work somehow. Surprisingly, this time there were thousands of messages like this:
ioctl failed on <directory name> ret -1 errno 28
Most of the reported directories had zero files/subdirectories. However, *most* of them were *not* empty...
What does this error message mean? Could someone shed more light on this, please? Should I get ready for a bad crash? ;-) (There seems to be no data loss so far. No new messages in dmesg, no unexpected system behavior.)
Andrej
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5804 bytes --]
next reply other threads:[~2010-11-29 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 21:02 Andrej Podzimek [this message]
2010-11-29 21:25 ` Errors during defragmentation Hugo Mills
2010-11-29 22:00 ` Andrej Podzimek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CF41500.8000804@podzimek.org \
--to=andrej@podzimek.org \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.