Re: strange btrfs sub list output

2011-06-01 Thread C Anthony Risinger
On Tue, May 31, 2011 at 2:32 PM, C Anthony Risinger wrote: > On Tue, May 31, 2011 at 1:50 PM, Andreas Philipp > wrote: >> >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> On 31.05.2011 19:40, C Anthony Risinger wrote: >>> On Tue, May 31, 2011 at 5:00 AM, Stephane Chazelas >>> wrote: >>>

[PATCH] make "btrfs filesystem label" command actually work

2011-06-01 Thread Fajar A. Nugraha
This simple patch makes "btrfs filesystem label" command actually work. On tmp branch, commit d1dc6a9, "btrfs filesystem label" functionality was introduced. However the commit lacks one component that lets "btrfs" accept "filesystem label" command. Test case: #===

[RFC PATCH] Btrfs-progs: Backref walking utilities

2011-06-01 Thread Liu Bo
This patch comes from one of project ideas on btrfs's wiki: Quote: Given a block number on a disk, the Btrfs metadata can find all the files and directories that use or care about that block. Some utilities to walk these back refs and print the results would help debug corruptions. Given an inode,

Re: btrfs error after using kernel 3.0-rc1

2011-06-01 Thread Fajar A. Nugraha
On Thu, Jun 2, 2011 at 4:48 AM, Chris Mason wrote: > Excerpts from Fajar A. Nugraha's message of 2011-06-01 08:22:40 -0400: >> On Wed, Jun 1, 2011 at 6:06 AM, Fajar A. Nugraha wrote: >> > While using btrfs as root on kernel 3.0-rc1, there was some errors (I >> > wasn't able to capture the error)

[BUG 3.0-rc1] oops during file removal, severe lock contention

2011-06-01 Thread Dave Chinner
Hi Folks, Running on 3.0-rc1 on an 8p/4G RAM VM with a 16TB filesystem (12 disk DM stripe) a 50 million inode 8-way fsmark creation workload via: $ /usr/bin/time ./fs_mark -D 1 -S0 -n 10 -s 0 -L 63 \ > -d /mnt/scratch/0 -d /mnt/scratch/1 \ > -d /mnt/scratch/2 -d /mnt/scratch/3 \ > -d /mnt

Re: different st_dev's in one subvolume

2011-06-01 Thread Stephane Chazelas
2011-06-02 01:39:41 +0100, Stephane Chazelas: [...] > /mnt/1# zstat +device ./**/* > . 25 > A 26 > A/B 27 > A/B/inB 27 > A/inA 26 > A.snap 28 > A.snap/B 23 > A.snap/inA 28 > > Why does A.snap/B have a different st_dev from A.snap's? [...] > If I create another snap of A or A.snap, the "B" in there

different st_dev's in one subvolume

2011-06-01 Thread Stephane Chazelas
Hiya, please consider this: ~# truncate -s1G ./a ~# mkfs.btrfs ./a ~# sudo mount -o loop ./a /mnt/1 ~# cd /mnt/1 /mnt/1# ls /mnt/1# btrfs sub c A Create subvolume './A' /mnt/1# btrfs sub c A/B Create subvolume 'A/B' /mnt/1# touch A/inA A/B/inB /mnt/1# btrfs sub snap A A.snap Create a snapshot of

Re: btrfs error after using kernel 3.0-rc1

2011-06-01 Thread liubo
On 06/01/2011 08:22 PM, Fajar A. Nugraha wrote: > On Wed, Jun 1, 2011 at 6:06 AM, Fajar A. Nugraha wrote: >> While using btrfs as root on kernel 3.0-rc1, there was some errors (I >> wasn't able to capture the error) that forced me to do hard reset. >> >> Now during startup system drops to busybox

btrfs-progs-unstable tmp branch build error

2011-06-01 Thread Fajar A. Nugraha
When building from tmp branch I got this error: mkfs.c: In function ‘main’: mkfs.c:730:6: error: ‘ret’ may be used uninitialized in this function mkfs.c:841:43: error: ‘parent_dir_entry’ may be used uninitialized in this function make: *** [mkfs.o] Error 1 "git blame" shows the last commit for b

Announcing btrfs-gui

2011-06-01 Thread Hugo Mills
Over the last few weeks, I've been playing with a foolish idea, mostly triggered by a cluster of people being confused by btrfs's free space reporting (df vs btrfs fi df vs btrfs fi show). I also wanted an excuse, and some code, to mess around in the depths of the FS data structures. Like al

Re: btrfs error after using kernel 3.0-rc1

2011-06-01 Thread Chris Mason
Excerpts from Fajar A. Nugraha's message of 2011-06-01 08:22:40 -0400: > On Wed, Jun 1, 2011 at 6:06 AM, Fajar A. Nugraha wrote: > > While using btrfs as root on kernel 3.0-rc1, there was some errors (I > > wasn't able to capture the error) that forced me to do hard reset. > > > > Now during start

btrfs kernel module crash

2011-06-01 Thread Jacques
Hi all, I have been using btrfs as my / partition on my fedora 14 box for a while now and until yesterday it was working a treat. Had an unexpected power fail during the night and now my os crashes when mounting / Most of my data is backed up, but there is some data which I don't want to lose on

Re: linux-next: build warninga in Linus' tree

2011-06-01 Thread Mitch Harder
On Tue, May 31, 2011 at 12:57 PM, David Sterba wrote: > Hi, > > On Mon, May 30, 2011 at 11:36:53AM +1000, Stephen Rothwell wrote: >> After merging the Linus' tree, today's linux-next build (powerpc >> ppc64_defconfig) produced these warnings: >> >> fs/btrfs/sysfs.c:76:26: warning: 'btrfs_root_attr

Re: [PATCH] Btrfs: don't save the inode cache if we are deleting this root

2011-06-01 Thread David Sterba
Hi, On Tue, May 31, 2011 at 03:33:33PM -0400, Josef Bacik wrote: > Signed-off-by: Josef Bacik Tested-by: David Sterba really needed in order to run xfstests, thanks. david -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kern

[GIT PULL] scrub fix for -rc2

2011-06-01 Thread Arne Jansen
Hi Chris, please pull from git://git.kernel.org/pub/scm/linux/kernel/git/arne/btrfs-unstable-arne.git for-chris the bio-reuse fix. I also included the small fix for the false BUG_ON in volumes.c. Here's the shortlog: Arne Jansen (2): btrfs: scrub: don't reuse bios and pages btrfs: f

Re: btrfs error after using kernel 3.0-rc1

2011-06-01 Thread Fajar A. Nugraha
On Wed, Jun 1, 2011 at 6:06 AM, Fajar A. Nugraha wrote: > While using btrfs as root on kernel 3.0-rc1, there was some errors (I > wasn't able to capture the error) that forced me to do hard reset. > > Now during startup system drops to busybox shell because it's unable > to mount root partition. >

Re: [3.0-rc1] kernel BUG at fs/btrfs/relocation.c:4285!

2011-06-01 Thread Tsutomu Itoh
Hi, liubo, (2011/06/01 18:42), liubo wrote: > On 06/01/2011 04:12 PM, liubo wrote: >> On 06/01/2011 03:44 PM, liubo wrote: On 05/31/2011 08:27 AM, Tsutomu Itoh wrote: The panic occurred when 'btrfs fi bal /test5' was executed. /test5 is as follows: # mount

Re: btrfs hang on brd

2011-06-01 Thread ajh mls
On 01/06/11 13:07, Adrian Hunter wrote: On 01/06/11 11:54, David Sterba wrote: On Tue, May 31, 2011 at 10:03:12AM +0300, Adrian Hunter wrote: Hi I seem to be able to get btrfs reproducibly to produce warnings and finally hang when running a stress test on a ramdisk. Testing was done using the

Re: btrfs hang on brd

2011-06-01 Thread Adrian Hunter
On 01/06/11 11:54, David Sterba wrote: On Tue, May 31, 2011 at 10:03:12AM +0300, Adrian Hunter wrote: Hi I seem to be able to get btrfs reproducibly to produce warnings and finally hang when running a stress test on a ramdisk. Testing was done using the "integration-test" branch of btrfs-unsta

Re: [3.0-rc1] kernel BUG at fs/btrfs/relocation.c:4285!

2011-06-01 Thread liubo
On 06/01/2011 04:12 PM, liubo wrote: > On 06/01/2011 03:44 PM, liubo wrote: >> > On 05/31/2011 08:27 AM, Tsutomu Itoh wrote: >> > The panic occurred when 'btrfs fi bal /test5' was executed. >> > >> > /test5 is as follows: >> > # mount -o space_cache,compress=lzo /dev/sdc3 /test

Re: btrfs hang on brd

2011-06-01 Thread David Sterba
On Tue, May 31, 2011 at 10:03:12AM +0300, Adrian Hunter wrote: > Hi > > I seem to be able to get btrfs reproducibly to > produce warnings and finally hang when running > a stress test on a ramdisk. > > Testing was done using the "integration-test" > branch of btrfs-unstable. Note that I also tes

Re: [3.0-rc1] kernel BUG at fs/btrfs/relocation.c:4285!

2011-06-01 Thread liubo
On 06/01/2011 03:44 PM, liubo wrote: > On 05/31/2011 08:27 AM, Tsutomu Itoh wrote: >> > The panic occurred when 'btrfs fi bal /test5' was executed. >> > >> > /test5 is as follows: >> > # mount -o space_cache,compress=lzo /dev/sdc3 /test5 >> > # >> > # btrfs fi sh /dev/sdc3 >> > Label: none uuid:

Re: [3.0-rc1] kernel BUG at fs/btrfs/relocation.c:4285!

2011-06-01 Thread liubo
On 05/31/2011 08:27 AM, Tsutomu Itoh wrote: > The panic occurred when 'btrfs fi bal /test5' was executed. > > /test5 is as follows: > # mount -o space_cache,compress=lzo /dev/sdc3 /test5 > # > # btrfs fi sh /dev/sdc3 > Label: none uuid: 38ec48b2-a64b-4225-8cc6-5eb08024dc64 > Total devices