On Mon, 12 Nov 2012 07:25:08 +0100, Jan Schmidt wrote:
In kernel, qgroupid 0 is a special number when we run the quota group
limit command.
So, we should not be able to create a quota group whose id is 0,
otherwise the kernel can't deal with it. Fix it.
>>>
>>> This is prob
Hi Miao,
On Mon, November 12, 2012 at 03:21 (+0100), Miao Xie wrote:
> On fri, 09 Nov 2012 10:33:52 +1100, Chris Samuel wrote:
>> On 08/11/12 20:55, Miao Xie wrote:
>>
>>> In kernel, qgroupid 0 is a special number when we run the quota group
>>> limit command.
>>>
>>> So, we should not be able to
On fri, 09 Nov 2012 10:33:52 +1100, Chris Samuel wrote:
> On 08/11/12 20:55, Miao Xie wrote:
>
>> In kernel, qgroupid 0 is a special number when we run the quota group
>> limit command.
>>
>> So, we should not be able to create a quota group whose id is 0,
>> otherwise the kernel can't deal with i
Fix the usage string to specify the correct '-f' option for input file,
not '-i'.
Signed-off-by: Ulrik Sverdrup
---
cmds-receive.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cmds-receive.c b/cmds-receive.c
index a8be6fa..c182175 100644
--- a/cmds-receive.c
+++ b/cmds-
Le 11/11/2012 16:20, Hugo Mills a écrit :
> Try mounting with clear_cache *once*, then remounting with
> space_cache,inode_cache *once*, and waiting for it to finish
> rebuilding the cache. Finally, remove all mention of the caches from
> your fstab and kernel command line before you next mount the
Le 11/11/2012 16:13, Bart Noordervliet a écrit :
> May I also suggest that you maybe shouldn't be running an experimental
> filesystem on a laptop that you can't go without?
I might well be retired before BTRFS is no more "experimental", but I
need its features now...
Otherwise I could go with “Z
On Sun, Nov 11, 2012 at 04:28:54PM +0100, Swâmi Petaramesh wrote:
> Le 11/11/2012 16:20, Hugo Mills a écrit :
> > You only need to mount with space_cache once, and after that it's
> > "sticky". What's probably happening is that you're mounting with
> > space_cache, which rebuilds the cache. Then, i
Le 11/11/2012 16:20, Hugo Mills a écrit :
> You only need to mount with space_cache once, and after that it's
> "sticky". What's probably happening is that you're mounting with
> space_cache, which rebuilds the cache. Then, if you reboot before it's
> finished rebuilding the cache, the cache isn't
On Sat, Nov 10, 2012 at 11:14:46PM +0100, Swâmi Petaramesh wrote:
> Hi,
>
> My BTRFS is mounted with space_cache,inode_cache , and I now get at boot
> time the following message :
>
> “btrfs: free space inode generation (0) did not match free space cache
> generation (189086)”
>
> Starting once
On Sun, Nov 11, 2012 at 3:26 PM, Swâmi Petaramesh wrote:
> I'm not going to take risks with this machine, which is my main laptop
> which I badly need to be in working order tomorrow morning (and #me
> having slept at night... ;-)
Without running different kernels, I don't think we can work with
Le 11/11/2012 15:21, Bart Noordervliet a écrit :
>> # uname -srv Linux 3.5.0-18-generic #29-Ubuntu SMP Fri Oct 19
>> 10:26:51 UTC 2012
> Could you first try with either 3.6 or a recent 3.7-rc build please?
> You can easily add them to Ubuntu by using their kernel ppa:
> http://kernel.ubuntu.com/~k
Le 11/11/2012 15:05, Bart Noordervliet a écrit :
> which kernel version are you running?
Hi Bart,
# uname -srv
Linux 3.5.0-18-generic #29-Ubuntu SMP Fri Oct 19 10:26:51 UTC 2012
--
Swâmi Petaramesh http://petaramesh.org PGP 9076E32E
Ne cherchez pas : Je ne suis pas sur Facebook.
--
To unsubsc
Hi Swami,
which kernel version are you running?
Regards,
Bart
On Sat, Nov 10, 2012 at 11:14 PM, Swâmi Petaramesh wrote:
> Hi,
>
> My BTRFS is mounted with space_cache,inode_cache , and I now get at boot
> time the following message :
>
> “btrfs: free space inode generation (0) did not match fr
13 matches
Mail list logo
