At Mon, 8 Jul 2013 13:59:03 +0200,
David Sterba wrote:
On Fri, Jul 05, 2013 at 07:47:47AM +0200, Takashi Iwai wrote:
I hit this problem when I moved the whole FS on
my workstation to
btrfs, and unfortunately in my case, I had to reinstall the whole
system from the scratch, and lose many data. This was the worst case
I met ever since Reiserfs over 10 years ago, so I gave up btrfs since
IIRC, this was the heavily patched 3.1.x based kernel from opensuse
12.1, right? Lots of backports were taken from sles kernel, but as there
were newer opensuse releases available, 12.1 did not get many updates
and some bugs were left. Using a recent kernel is recommended.
This was with a custom built kernel, 3.9-rc-something, IIRC. So this
must have been an upstream bug.
-ENOSPC is unavoidable as a nature of COW, especially when
snapshots are taken automatically. But, the behavior like this
(refusing any actions including mount) is a literally disaster, which
must not happen. If mount may be refused, at least a proper fsck must
be provided instead of a random tool.
Yeah the enospc situation is far from perfect, but has improved over
I hope it sincerely :)
Though, as someone already mentioned in another same thread on FACTORY
ML, a sane automatic recovery would be really required, no matter how
stable the filesystem is. A breakage may happen not only by a
software bug but also by faulty hardware. The lack of fsck is one of
the biggest hindrances for recommending btrfs for daily use, even if
it's just a matter of mental ease.
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org