From: dima <dolenin@parallels.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: system hangs after deleting bad file
Date: Mon, 24 Oct 2011 03:48:14 +0000 (UTC) [thread overview]
Message-ID: <loom.20111024T054315-615@post.gmane.org> (raw)
In-Reply-To: BwKod0ky1uB@helmut.hullen.de
Hello,
I had a similar problem.
Some files (2-3) got corrupted in my /home subvolume for no apparent reason.
Trying to access the files gives kernel oops. Sometimes it freezes the machine,
sometimes I am back to my console without any problems.
Then I switched to the latest 3.1rc and freezes were gone (though I still had
the kernel oops).
(I did not try the repair program fearing that it would do more bad than good.
After all, my / subvolume was fine and i still could mount /home)
But to tackle the problems with corrupted files I had to create a new subvolume
for /home, tranfer the files from the old one (minus the corrupted files) and
delete the old subvolume.
Though still btrfsck would give me errors trying to access some inode. But I
could mount and use all my subvolumes with no problems.
Then... I re-created btrfs with the latest btrfs-tools and installed the latest
3.1rc from the very beginning.
So far, it is working fine and the situation with disk I/O has greatly improved.
I think you may want to try to upgrade to the latest 3.1rc and at the very least
you (hopefully) should not be getting hard freezes any more.
best
~dima
next prev parent reply other threads:[~2011-10-24 3:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-22 9:52 system hangs after deleting bad file Helmut Hullen
2011-10-22 12:37 ` hurikhan77+btrfs
2011-10-24 3:48 ` dima [this message]
2011-10-24 15:04 ` Helmut Hullen
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=loom.20111024T054315-615@post.gmane.org \
--to=dolenin@parallels.com \
--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.