From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: linux v3.1 with btrfs-work: oops when deleting files
Date: 26 Oct 2011 20:52:00 +0200 [thread overview]
Message-ID: <Bwa12Zyi1uB@helmut.hullen.de> (raw)
In-Reply-To: <CAMthOuNq2E+sQxmkTBHUbiPyPCthVKsSaZTo1hVV1rgOb9NJqQ@mail.gmail.com>
Hallo, Kai,
Du meintest am 26.10.11:
> I can run "find -type f" for directories I suspect corrupted files
> in, and I see errors in dmesg if it happens to contain bad files. But
> no oopses and the system remains stable. If I mount the filesystem
> read-only I can even read these files without oopses,
Ok - may be I need this hint too sometimes in the next weeks.
> But since I do not have enough capacity to hold both my original
> backup (home files only, the system is already outdated) and the
> complete btrfs system (combined multiple partitions from an lvm setup
> into one btrfs volume with subvolumes) I cannot just recreate the
> same file system from scratch. Looks like I have to buy another hard
> disk (going to become expensive soon anyway) and rsync over to a
> fresh btrfs.
Same problem here. I fear that I have to copy my btrfs cluster (more
than 4 TByte on 3 disks) to another 3-disk cluster - last week that
would have been 200 Euro, now it may be 300 Euro.
I don't dare the way
add a 4th 2-TByte disk
balance
remove the bad disk
(that was the major reason for me using btrfs - adding bigger disks,
removing smaller disks ...)
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2011-10-26 18:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 4:48 linux v3.1 with btrfs-work: oops when deleting files Kai Krakow
2011-10-26 9:35 ` dima
2011-10-26 10:25 ` Helmut Hullen
2011-10-27 7:09 ` dima
2011-10-26 17:40 ` Kai Krakow
2011-10-26 18:52 ` Helmut Hullen [this message]
2011-10-27 1:15 ` dima
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=Bwa12Zyi1uB@helmut.hullen.de \
--to=hullen@t-online.de \
--cc=helmut@hullen.de \
--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.