On Sat, 4 Jan 2014 06:10:14 AM Duncan wrote:
Btrfs remains under development and there are clear warnings
about using it without backups one hasn't tested recovery from
or are not otherwise prepared to actually use. It's stated in
multiple locations on the wiki; it's stated on the kernel
On Sat, 4 Jan 2014 12:57:02 AM Dave wrote:
I find myself annoyed by the constant disclaimers I
read on this list, about the experimental status of Btrfs, but it's
apparent that this hasn't sunk in for everyone.
Btrfs will no longer marked as experimental in the kernel as of 3.13.
Unless
Chris Samuel posted on Sat, 04 Jan 2014 22:20:20 +1100 as excerpted:
On Sat, 4 Jan 2014 06:10:14 AM Duncan wrote:
Btrfs remains under development and there are clear warnings about
using it without backups one hasn't tested recovery from or are not
otherwise prepared to actually use.
On Sat, 2014-01-04 at 06:10 +, Duncan wrote:
Chris Murphy posted on Fri, 03 Jan 2014 16:22:44 -0700 as excerpted:
I would not make this option persistent by putting it permanently in the
grub.cfg; although I don't know the consequence of always mounting with
degraded even if not
On Sat, 2014-01-04 at 22:28 +1100, Chris Samuel wrote:
On Sat, 4 Jan 2014 12:57:02 AM Dave wrote:
I find myself annoyed by the constant disclaimers I
read on this list, about the experimental status of Btrfs, but it's
apparent that this hasn't sunk in for everyone.
Btrfs will no longer
On 2014-01-04 15:51, Chris Mason wrote:
I added mount -o degraded just because I wanted the admin to be notified
of failures. Right now it's still the most reliable way to notify them,
but I definitely agree we can do better.
I think that we should align us to what the others raid subsystem
Sending the exact same send stream to two different machines, on
one of them I am getting:
ERROR: BTRFS_IOC_SET_RECEIVED_SUBVOL failed. Inappropriate ioctl for device
The other machine is fine. Investigating, I find that the working
machine is 64-bit userspace and kernel. The failing
On Jan 3, 2014, at 7:59 PM, Jim Salter j...@jrs-s.net wrote:
On 01/03/2014 07:27 PM, Chris Murphy wrote:
This is the wrong way to solve this. /etc/grub.d/10_linux is subject to
being replaced on updates. It is not recommended it be edited, same as for
grub.cfg. The correct way is as I
Chris Mason posted on Sat, 04 Jan 2014 14:51:23 + as excerpted:
It'll pick the latest generation number and use that one as the one true
source. For the others you'll get crc errors which make it fall back to
the latest one. If the two have exactly the same generation number,
we'll have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/01/14 09:25, Marc MERLIN wrote:
Is there even a reason for this not to become a default mount option
in newer kernels?
autodefrag can go insane because it is unbounded. For example I have a
4GB RAM system (3.12, no gui) that kept hanging. I
On 01/04/2014 02:18 PM, Chris Murphy wrote:
I'm not sure what else you're referring to?(working on boot
environment of btrfs)
Just the string of caveats regarding mounting at boot time - needing to
monkeypatch 00_header to avoid the bogus sparse file error (which,
worse, tells you to press
Hi Chris,
I ran btrfsck on my volume with the repair option. When I re-run it,
I get the same errors as before.
Did you try mounting with -o recovery first?
https://btrfs.wiki.kernel.org/index.php/Problem_FAQ
No, I did not.
In fact, I had visited the FAQ before, and my understanding was,
On 01/04/2014 01:10 AM, Duncan wrote:
The example given in the OP was of a 4-device raid10, already the
minimum number to work undegraded, with one device dropped out, to
below the minimum required number to mount undegraded, so of /course/
it wouldn't mount without that option.
The issue
Oh gosh, I don't know what went wrong with my btrfs root filesystem, and I
probably will never know, too:
The sudo balance start / was running fine for about 4 or 5 hours, running
at a system load of ~3 when balance status / told me the balancing was on
its way and had completed 19 out of 23
On 12/30/2013 02:51 AM, Liu Bo wrote:
So after transaction is aborted, we need to cleanup inode resources by
calling btrfs_invalidate_inodes(), and btrfs_invalidate_inodes() hopes
roots' refs to be zero in old times and sets a WARN_ON(), however, this
is not always true within cleaning up
hi all
i am using up to date debian sid with xfce desktop environment. i am
using Linux 3.13-rc6-amd64 #1 SMP Debian 3.13~rc6-1~exp1 (2013-12-30)
x86_64 GNU/Linux from experimental.
i have installed usbmount to auto mount all the devices connected
through USB.
[cmd# 1] i have created btrfs
16 matches
Mail list logo
