Re: BUG at fs/btrfs/print-tree when trying to mount after a crash

2013-06-18 Thread Duncan
Michael Zugelder posted on Mon, 17 Jun 2013 21:10:27 +0200 as excerpted: Hi, my laptop with a btrfs on dm-crypt on SSD freezed today shortly after resuming from suspend (it doesn't normally do that). I was running a self compiled 3.9.6 at this point. There should be around 20 of 114 GiB

My multi-device btrfs (3*2TB) won't mount anymore.

2013-06-18 Thread Retro Pirate
My multi-device btrfs (3*2TB) won't mount anymore. The fs was created with lubuntu 13.04 (amd64) and the default kernel with -n 8192 -d single -m raid1, first with two devices the third was added later. Quotas where enabled after fs creation (btrfs quota enable) but nothing else, there are several

Re: BUG at fs/btrfs/print-tree when trying to mount after a crash

2013-06-18 Thread Michael Zugelder
Thanks for the reply. On Tue, 2013-06-18 at 06:04 +, Duncan wrote: [...] 1) I had an similar issue some time back that turned out to be a corrupted space-cache. Try mounting with the nospace_cache option. If that works that's it; mount with the clear_cache option to clear the bad

Re: [PATCH] Btrfs: fix wrong csum clone when doing relocation

2013-06-18 Thread Josef Bacik
On Tue, Jun 18, 2013 at 11:13:37AM +0800, Miao Xie wrote: From: Josef Bacik jba...@fusionio.com Patch Btrfs: remove btrfs_sector_sum structure introduced a problem that we copied the checksum value to the wrong address when doing relocation. The reason is: It is very likely that one

Re: My multi-device btrfs (3*2TB) won't mount anymore.

2013-06-18 Thread cwillu
Does anything show up in dmesg when you mount? If mount just hangs, do an alt-sysrq-w, and then post what that sends to dmesg. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at

Re: hang on 3.9, 3.10-rc5

2013-06-18 Thread Sage Weil
On Wed, 12 Jun 2013, Sage Weil wrote: On Tue, 11 Jun 2013, Chris Mason wrote: Quoting Sage Weil (2013-06-11 11:43:30) I'm also seeing this hang regularly with both 3.9 and 3.10-rc5. Is this is a known problem? In this case there is no powercycling; just a regular ceph-osd workload.

Re: hang on 3.9, 3.10-rc5

2013-06-18 Thread Josef Bacik
On Tue, Jun 11, 2013 at 11:43:30AM -0400, Sage Weil wrote: I'm also seeing this hang regularly with both 3.9 and 3.10-rc5. Is this is a known problem? In this case there is no powercycling; just a regular ceph-osd workload. Have you gotten sysrq+w? Can you tell me where

Re: hang on 3.9, 3.10-rc5

2013-06-18 Thread Chris Mason
Quoting Sage Weil (2013-06-18 11:56:37) On Wed, 12 Jun 2013, Sage Weil wrote: On Tue, 11 Jun 2013, Chris Mason wrote: Quoting Sage Weil (2013-06-11 11:43:30) I'm also seeing this hang regularly with both 3.9 and 3.10-rc5. Is this is a known problem? In this case there is no

Re: hang on 3.9, 3.10-rc5

2013-06-18 Thread Chris Mason
Quoting Josef Bacik (2013-06-18 12:37:06) On Tue, Jun 11, 2013 at 11:43:30AM -0400, Sage Weil wrote: I'm also seeing this hang regularly with both 3.9 and 3.10-rc5. Is this is a known problem? In this case there is no powercycling; just a regular ceph-osd workload. Have you gotten

Re: hang on 3.9, 3.10-rc5

2013-06-18 Thread Jon Nelson
Josef Bacik jbacik at fusionio.com writes: On Tue, Jun 11, 2013 at 11:43:30AM -0400, Sage Weil wrote: I'm also seeing this hang regularly with both 3.9 and 3.10-rc5. Is this is a known problem? In this case there is no powercycling; just a regular ceph-osd workload. .. I'm able to

[PATCH] Btrfs: move btrfs_truncate_page to btrfs_cont_expand instead of btrfs_truncate V2

2013-06-18 Thread Josef Bacik
This has plagued us forever and I'm so over working around it. When we truncate down to a non-page aligned offset we will call btrfs_truncate_page to zero out the end of the page and write it back to disk, this will keep us from exposing stale data if we truncate back up from that point. The

[PATCH] Btrfs: do not ignore errors when truncating the free space cache inode

2013-06-18 Thread Djalal Harouni
btrfs_check_trunc_cache_free_space() tries to check if there is enough space for cache inode truncation but it fails. Currently this function always returns success even if there is no enough space. Fix this by returning the -ENOSPC error code. Signed-off-by: Djalal Harouni tix...@opendz.org ---

Re: [PATCH] Btrfs: do not ignore errors when truncating the free space cache inode

2013-06-18 Thread Miao Xie
It was fixed by Wei Yongjun http://marc.info/?l=linux-btrfsm=136910396606489w=2 Thanks Miao On tue, 18 Jun 2013 22:57:41 +0100, Djalal Harouni wrote: btrfs_check_trunc_cache_free_space() tries to check if there is enough space for cache inode truncation but it fails. Currently this

[PATCH V4] Btrfs: remove btrfs_sector_sum structure

2013-06-18 Thread Miao Xie
Using the structure btrfs_sector_sum to keep the checksum value is unnecessary, because the extents that btrfs_sector_sum points to are continuous, we can find out the expected checksums by btrfs_ordered_sum's bytenr and the offset, so we can remove btrfs_sector_sum's bytenr. After removing