On Tuesday 2009-03-03 16:40, Josef Bacik wrote: >> >> The following oops was obtained by doing some copying; it's tainted-P by >> nvidia but maybe it still gives some hints. >> The testcase is basically >> >> $ rsync -HPSav a/ b/ >> >> where by a/ is a collection of kernel trees, and b/ is a fresh btrfs. >> >> $ ls -l a/ >> drwxr-xr-x 19 jengelh users 4096 Jan 10 07:32 linux17 >> drwxr-xr-x 19 jengelh users 4096 Jan 10 07:34 linux18 >> drwxr-xr-x 19 jengelh users 4096 Jan 10 07:34 linux19 >> drwxr-xr-x 19 jengelh users 4096 Jan 10 07:34 linux20 >> drwxr-xr-x 19 jengelh users 4096 Jan 10 07:35 linux21 >> drwxr-xr-x 19 jengelh users 4096 Jan 10 07:35 linux22 >> drwxr-xr-x 19 jengelh users 4096 Jan 10 07:35 linux23 >> drwxr-xr-x 20 jengelh users 4096 Jan 10 07:35 linux24 >> drwxr-xr-x 21 jengelh users 4096 Jan 10 07:36 linux25 >> drwxr-xr-x 21 jengelh users 4096 Jan 10 07:36 linux26 >> drwxr-xr-x 22 jengelh users 4096 Jan 10 07:37 linux27 >> drwxr-xr-x 22 jengelh users 4096 Jan 10 07:37 linux28 > >ENOSPC, sorry :)
Ah heh, could be a cause. Even so, there is still "plenty" of space (loop1 with btrfs is also 4184064K in size): Filesystem Type 1K-blocks Used Available Use% Mounted on /dev/loop0 xfs 4184064 3676644 507420 88% /lo/kernel -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
