Duncan posted on Mon, 06 Apr 2015 09:20:12 + as excerpted:
Pavel Volkov posted on Mon, 06 Apr 2015 10:40:03 +0300 as excerpted:
By the way, is there any way to see which options are enabled on a
local filesystem without having to try mounting it with old kernel and
checking dmesg?
On Mon, 6 Apr 2015 07:40:03 AM Pavel Volkov wrote:
On Sunday, April 5, 2015 1:04:17 PM MSK, Hugo Mills wrote:
That's these, I think:
#define BTRFS_FEATURE_INCOMPAT_BIG_METADATA (1ULL 5)
#define BTRFS_FEATURE_INCOMPAT_EXTENDED_IREF(1ULL 6)
so it's definitely -O^extref. I
On Mon, 6 Apr 2015 03:21:18 AM Duncan wrote:
So... for 3.2 compatibility, extref must not be enabled (tho it's now the
default and AFAIK there's no way to actually disable it, only enable, so
an old btrfs-tools would have to be used that doesn't enable it by
default), AND the nodesize must
On Sunday, April 5, 2015 1:04:17 PM MSK, Hugo Mills wrote:
That's these, I think:
#define BTRFS_FEATURE_INCOMPAT_BIG_METADATA (1ULL 5)
#define BTRFS_FEATURE_INCOMPAT_EXTENDED_IREF(1ULL 6)
so it's definitely -O^extref. I don't see where big_metadata comes
from, though. That's not a
Pavel Volkov posted on Mon, 06 Apr 2015 10:40:03 +0300 as excerpted:
On Sunday, April 5, 2015 1:04:17 PM MSK, Hugo Mills wrote:
That's these, I think:
#define BTRFS_FEATURE_INCOMPAT_BIG_METADATA (1ULL 5)
#define BTRFS_FEATURE_INCOMPAT_EXTENDED_IREF(1ULL 6)
so it's definitely
On Mon, Apr 06, 2015 at 10:40:03AM +0300, Pavel Volkov wrote:
On Sunday, April 5, 2015 1:04:17 PM MSK, Hugo Mills wrote:
That's these, I think:
#define BTRFS_FEATURE_INCOMPAT_BIG_METADATA (1ULL 5)
#define BTRFS_FEATURE_INCOMPAT_EXTENDED_IREF(1ULL 6)
so it's definitely
Hugo Mills posted on Sun, 05 Apr 2015 10:04:17 + as excerpted:
On Sun, Apr 05, 2015 at 03:30:47AM +, Russell Coker wrote:
On Sun, 5 Apr 2015 03:16:21 AM Duncan wrote:
Hugo Mills posted on Sat, 04 Apr 2015 13:00:47 + as excerpted:
On Sat, Apr 04, 2015 at 12:55:08PM +,
On Sun, Apr 05, 2015 at 03:30:47AM +, Russell Coker wrote:
On Sun, 5 Apr 2015 03:16:21 AM Duncan wrote:
Hugo Mills posted on Sat, 04 Apr 2015 13:00:47 + as excerpted:
On Sat, Apr 04, 2015 at 12:55:08PM +, Russell Coker wrote:
As an aside are there options to mkfs.btrfs that
On Fri, 3 Apr 2015 05:14:12 AM Duncan wrote:
Well, btrfs itself isn't really stable yet... Stable series should be
stable at least to the extent that whatever you're using in them is, but
with btrfs itself not yet entirely stable...
Also for stable operation you want both forward and
On Sat, Apr 04, 2015 at 12:55:08PM +, Russell Coker wrote:
On Fri, 3 Apr 2015 05:14:12 AM Duncan wrote:
Well, btrfs itself isn't really stable yet... Stable series should be
stable at least to the extent that whatever you're using in them is, but
with btrfs itself not yet entirely
On Sun, 5 Apr 2015 03:16:21 AM Duncan wrote:
Hugo Mills posted on Sat, 04 Apr 2015 13:00:47 + as excerpted:
On Sat, Apr 04, 2015 at 12:55:08PM +, Russell Coker wrote:
As an aside are there options to mkfs.btrfs that would make a
filesystem mountable by kernel 3.2.65? If so I'll
Hugo Mills posted on Sat, 04 Apr 2015 13:00:47 + as excerpted:
On Sat, Apr 04, 2015 at 12:55:08PM +, Russell Coker wrote:
As an aside are there options to mkfs.btrfs that would make a
filesystem mountable by kernel 3.2.65? If so I'll file a Debian/Jessie
bug report requesting that
I've get it several times, after rebooting or unclean shutdown system.
This is very strange bug, because if i reboot, and mount it from live
cd, all that okay, and after reboot in system, system successful mount
all and working good.
i did try to found any previous issues on it, and found
So cool, thanks Hugo :)
2015-04-02 14:46 GMT+03:00 Hugo Mills h...@carfax.org.uk:
On Thu, Apr 02, 2015 at 02:38:24PM +0300, Timofey Titovets wrote:
I've get it several times, after rebooting or unclean shutdown system.
This is very strange bug, because if i reboot, and mount it from live
cd,
On Thu, Apr 02, 2015 at 02:38:24PM +0300, Timofey Titovets wrote:
I've get it several times, after rebooting or unclean shutdown system.
This is very strange bug, because if i reboot, and mount it from live
cd, all that okay, and after reboot in system, system successful mount
all and
Roman Mamedov posted on Thu, 02 Apr 2015 19:13:12 +0500 as excerpted:
Yeah I believe I just hit that in 3.14.37, system unbootable (locks up
at Scanning for Btrfs filesystems), resulted in a many hour downtime
as it was a remote system w/o IPMI. Fine after a reboot to 3.14.34. Too
bad that
On Thu, 2 Apr 2015 11:46:08 +
Hugo Mills h...@carfax.org.uk wrote:
On Thu, Apr 02, 2015 at 02:38:24PM +0300, Timofey Titovets wrote:
I've get it several times, after rebooting or unclean shutdown system.
This is very strange bug, because if i reboot, and mount it from live
cd, all
17 matches
Mail list logo
