From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: filesystem full when it's not? out of inodes? huh?
Date: 26 Feb 2012 10:10:00 +0100 [thread overview]
Message-ID: <C3b00H6y1uB@helmut.hullen.de> (raw)
In-Reply-To: <pan.2012.02.26.08.52.06@cox.net>
Hallo, Duncan,
Du meintest am 26.02.12:
> It's astonishing to me the number of people that come in here
> complaining about problems with a filesystem the kernel option of
> which says
> Title:
> Btrfs filesystem (EXPERIMENTAL) Unstable disk format
> Description (excerpt):
> Btrfs is highly experimental, and THE DISK FORMAT IS NOT YET
> FINALIZED. You should say N here unless you are interested in
> testing Btrfs with non-critical data.
Just take a look at Fedora.
The maintainers had planned to use btrfs as standard filesystem for
Fedora 16 (but haven't done so), they had planned to use btrfs for
Fedora 17, but perhaps hesitate, see
https://fedorahosted.org/fesco/ticket/704
There are some other distributions which also seem to (perhaps) follow
the "bleading edge".
And therefore end users believe that using btrfs is safe.
(I've learned my lesson ...)
Just for the record: using btrfs (when it runs stable) may reduce many
other problems on my system. I'm still hoping.
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2012-02-26 9:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 1:55 filesystem full when it's not? out of inodes? huh? Brian J. Murrell
2012-02-26 2:10 ` Fahrzin Hemmati
2012-02-26 2:16 ` Brian J. Murrell
2012-02-26 2:37 ` Fahrzin Hemmati
2012-02-26 3:57 ` Brian J. Murrell
2012-02-26 4:05 ` Fahrzin Hemmati
2012-03-09 22:02 ` Johannes Hirte
2012-02-26 8:52 ` Duncan
2012-02-26 9:10 ` Helmut Hullen [this message]
2012-02-26 9:41 ` Duncan
2012-03-03 10:25 ` Chris Samuel
2012-02-26 5:45 ` Brian J. Murrell
2012-02-26 5:50 ` Fahrzin Hemmati
2012-02-26 6:14 ` Brian J. Murrell
2012-02-26 7:19 ` Jérôme Poulin
2012-02-26 19:43 ` Brian J. Murrell
2012-02-26 11:00 ` Hugo Mills
2012-03-02 11:50 ` Brian J. Murrell
2012-03-02 12:23 ` Fajar A. Nugraha
2012-02-26 19:37 ` Daniel Lee
2012-02-26 19:48 ` Brian J. Murrell
2012-02-26 19:52 ` Daniel Lee
2012-02-26 20:05 ` Brian J. Murrell
2012-02-26 20:25 ` Daniel Lee
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=C3b00H6y1uB@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).