On Tue, Dec 30, 2014 at 07:29:10PM -0800, Dave Stevens wrote:
I have a well tested and working fine Centos5-Xen system.
Accumulated cruft from various development efforts make it desirable
to redo the install. Currently a RAID-10 ext4 filesystem with LVM
and 750G of storage. There's a hot
Great! The root cause of missing file is fixed!
Thanks a lot!
Qu
Original Message
Subject: Re: [PATCH] Btrfs: don't delay inode ref updates during log replay
From: Marc MERLIN m...@merlins.org
To: Chris Mason c...@fb.com, Qu Wenruo quwen...@cn.fujitsu.com, Roman
Mamedov
Chris, you rule, I applied this to 3.16.7 and my problem went away.
Tested-By: Marc MERLIN m...@merlins.org
Happy new year! :)
Marc
On Wed, Dec 31, 2014 at 01:30:13PM -0500, Chris Mason wrote:
Commit 1d52c78afbb (Btrfs: try not to ENOSPC on log replay) added a
check to skip delayed inode
On Mon, Dec 29, 2014 at 6:52 PM, Gui Hecheng guihc.f...@cn.fujitsu.com wrote:
Signed-off-by: Gui Hecheng guihc.f...@cn.fujitsu.com
Reviewed-by: Satoru Takeuchi takeuchi_sat...@jp.fujitsu.com
---
changelog
v1-v2:
s/\'E\'(EiB)/or \'E\'(EiB)/ as suggested by Satoru,
Signed-off-by: Khaled Ahmed khaled@gmail.com
---
fs/btrfs/qgroup.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/btrfs/qgroup.c b/fs/btrfs/qgroup.c
index 48b60db..b85200d 100644
--- a/fs/btrfs/qgroup.c
+++ b/fs/btrfs/qgroup.c
@@ -2408,14 +2408,14 @@ int
Original Message
Subject: How to handle remove media (was: Re: What about not warn on
some abort_transaction() case whose reason is known?)
From: Martin Steigerwald mar...@lichtvoll.de
To: Qu Wenruo quwen...@cn.fujitsu.com
Date: 2014年12月31日 18:24
I am cc´ing this to fsdevel
Roger Binns posted on Thu, 01 Jan 2015 12:12:31 -0800 as excerpted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/31/2014 05:26 PM, Chris Samuel wrote:
I suspect this is a knock-on effect of the fact that (unless this has
changed recently IIRC) RAID-1 with btrfs will only mirrors
Add btrfs_get_extent() and btrfs_punch_hole() for btrfs-progs.
Btrfs_get_extent() will act much like kernel one, return the first
extent that covers the given range.
The difference will be that progs btrfs_get_extent() can't handle
no-holes feature, which means caller should handle it carefully.
Record every file extent discontinuous hole in inode_record using a
rb_tree member.
Before the patch, btrfsck will only record the first file extent hole by
using first_extent_gap, that's good for detecting error, but not
suitable for fixing it.
This patch provides the ability to record every
Since orphan extents are handled in previous patches, now just punch
holes to fill the file extents hole.
Also since now btrfsck is aware of whether the inode has orphan file
extent, allow repair_inode_no_item() to determine filetype according to
orphan file extent.
Signed-off-by: Qu Wenruo
In some fs tree leaf/node corruption case, file extents may be lost, but
in extent tree, its record may still exists.
This provide the possibility for such orphan file extents to be
recovered even we can't recover its compression and other info, we can
still insert it as a normal non-compression
11 matches
Mail list logo
