On Mon, Feb 24, 2014 at 06:32:14AM +, Duncan wrote:
Marc MERLIN posted on Sun, 23 Feb 2014 21:51:03 -0800 as excerpted:
In the end I pinned it down to this:
3.13.5's kernel/userland interface fails if my kernel is 64bit and my
userland 32bit.
This is a known issue. There's patches
Hugo Mills posted on Mon, 24 Feb 2014 08:29:38 + as excerpted:
On Mon, Feb 24, 2014 at 06:32:14AM +, Duncan wrote:
This is a known issue. There's patches in the pipeline for 32-bit
userspace on a 64-bit kernel, already.
If you mean my recent patch, that's only for receive.
The test 013 couldn't work because here lacked start.
This patch fix it.
Signed-off-by: Zhang Zhen zhenzhang.zh...@huawei.com
---
tests/btrfs/013 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/btrfs/013 b/tests/btrfs/013
index 7620fcc..fb81663 100644
---
Hi Zhang,
On 02/24/2014 06:51 PM, ZhangZhen wrote:
The test 013 couldn't work because here lacked start.
This patch fix it.
Signed-off-by: Zhang Zhenzhenzhang.zh...@huawei.com
---
tests/btrfs/013 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/btrfs/013
kindly ignore this patch. Though it correct that we need to
start from devid 0 to scan. But the individual scan is broken
well before this patch. So to fix all together a patch bundle
is sent to the mailing list including this
Thanks Anand
On 02/04/14 04:33 PM, Anand Jain wrote:
During disk
get_fs_info() provides the info of the specific
device/devid, however when we delete the missing disk
the super-block on the disk isn't cleared, and since
btrfs-progs makes its decision by reading the disk super
block, so it doesn't know about the kernel previous action,
And now when we tried to
From: Anand Jain anand.j...@oracle.com
as of now, when we replace a disk, it is added to the
dev list with devid 0. And we fail to obtain details
of devid 0 because we don't query devid 0 at all.
reproducer:
btrfs rep start /dev/sdb /dev/sdf /btrfs
btrfs fi show
Label: none uuid:
From: Anand Jain anand.j...@oracle.com
The user land progs needs a simple way to see
the raw list of disks and its parameters as seen
by the btrfs kernel.
As of now btrfs-devlist uses this ioctl.
Signed-off-by: Anand Jain anand.j...@oracle.com
---
v2: add more parameter to get from the kernel
From: Anand Jain anand.j...@oracle.com
This is a small (debug) program to dump the device list
in the raw format from the btrfs kernel.
here I use ioctl which was introduced in the below kernel
patch
btrfs: introduce BTRFS_IOC_GET_DEVS
Signed-off-by: Anand Jain anand.j...@oracle.com
---
v2: add
Regression test for btrfs incremental send issue where a rmdir instruction
is sent against an orphan directory inode which is not empty yet, causing
btrfs receive to fail when it attempts to remove the directory.
This issue is fixed by the following linux kernel btrfs patch:
Btrfs: fix send
Regression test for a btrfs incremental send issue where invalid paths for
utimes, chown and chmod operations were sent to the send stream, causing
btrfs receive to fail.
If a directory had a move/rename operation delayed, and none of its parent
directories, except for the immediate one, had
To avoid repeating detection of fssum presence in many btrfs tests, as
suggested by Dave Chinner.
Signed-off-by: Filipe David Borba Manana fdman...@gmail.com
---
common/rc |7 +++
tests/btrfs/007 |5 +
tests/btrfs/016 |5 +
tests/btrfs/030 |5 +
On Mon, Feb 24, 2014 at 5:25 AM, Dave Chinner da...@fromorbit.com wrote:
On Wed, Feb 19, 2014 at 02:32:32PM +, Filipe David Borba Manana wrote:
Regression test for btrfs incremental send issue where a rmdir instruction
is sent against an orphan directory inode which is not empty yet,
When we split an extent state there's no need to start the rbtree search
from the root node - we can start it from the original extent state node,
since we would end up in its subtree if we do the search starting at the
root node anyway.
Signed-off-by: Filipe David Borba Manana fdman...@gmail.com
We found btrfsck will output backrefs mismatch while the filesystem
is defenitely ok.
The problem is that check_block() don't return right value,which
makes btrfsck won't walk all tree blocks thus we don't get a consistent
filesystem, we will fail to check extent refs etc.
Reported-by: Gui
On Mon, Feb 24, 2014 at 11:56:23AM +, Filipe David Borba Manana wrote:
To avoid repeating detection of fssum presence in many btrfs tests, as
suggested by Dave Chinner.
Signed-off-by: Filipe David Borba Manana fdman...@gmail.com
---
common/rc |7 +++
tests/btrfs/007 |
On Mon, Feb 24, 2014 at 12:23 PM, Dave Chinner da...@fromorbit.com wrote:
On Mon, Feb 24, 2014 at 11:56:23AM +, Filipe David Borba Manana wrote:
To avoid repeating detection of fssum presence in many btrfs tests, as
suggested by Dave Chinner.
Signed-off-by: Filipe David Borba Manana
On Thu, Feb 20, 2014 at 6:57 PM, David Sterba dste...@suse.cz wrote:
On Wed, Feb 19, 2014 at 11:10:41AM -0500, Austin S Hemmelgarn wrote:
Currently, btrfs balance start fails when trying to convert metadata or
system chunks to dup profile on filesystems with multiple devices. This
requires
On 2014-02-24 08:37, Ilya Dryomov wrote:
On Thu, Feb 20, 2014 at 6:57 PM, David Sterba dste...@suse.cz wrote:
On Wed, Feb 19, 2014 at 11:10:41AM -0500, Austin S Hemmelgarn wrote:
Currently, btrfs balance start fails when trying to convert metadata or
system chunks to dup profile on filesystems
FYI, this crash was reproducible and was happening when using rsync
with --inplace option on a fragmented file:
# filefrag *
bayes_journal: 2 extents found
bayes_seen: 988 extents found
bayes_toks: 41 extents found
rsync process was hanging here:
var/lib/amavis/.spamassassin/
Hi,
I am trying to enhance GParted (http://www.gparted.org/) to better
support btrfs, specifically multi-device ones. GParted displays the
busy status (mounted or not) and the mount point of each partition.
For a single device file system this is easy. Entry in /proc/mounts
for the partition
On Mon, Feb 24, 2014 at 01:48:55PM +, Mike Fleetwood wrote:
Hi,
I am trying to enhance GParted (http://www.gparted.org/) to better
support btrfs, specifically multi-device ones. GParted displays the
busy status (mounted or not) and the mount point of each partition.
For a single
On Mon, Feb 24, 2014 at 3:44 PM, Austin S Hemmelgarn
ahferro...@gmail.com wrote:
On 2014-02-24 08:37, Ilya Dryomov wrote:
On Thu, Feb 20, 2014 at 6:57 PM, David Sterba dste...@suse.cz wrote:
On Wed, Feb 19, 2014 at 11:10:41AM -0500, Austin S Hemmelgarn wrote:
Currently, btrfs balance start
On 2014-02-24 09:12, Ilya Dryomov wrote:
On Mon, Feb 24, 2014 at 3:44 PM, Austin S Hemmelgarn
ahferro...@gmail.com wrote:
On 2014-02-24 08:37, Ilya Dryomov wrote:
On Thu, Feb 20, 2014 at 6:57 PM, David Sterba dste...@suse.cz wrote:
On Wed, Feb 19, 2014 at 11:10:41AM -0500, Austin S Hemmelgarn
On Mon, Feb 24, 2014 at 1:45 PM, Tomasz Chmielewski t...@virtall.com wrote:
FYI, this crash was reproducible and was happening when using rsync
with --inplace option on a fragmented file:
# filefrag *
bayes_journal: 2 extents found
bayes_seen: 988 extents found
bayes_toks: 41 extents found
Since commit c652e4ef changes default metadata blocksize, update
corresponding options in man page.
Signed-off-by: Rakesh Pandit rak...@tuxera.com
---
man/mkfs.btrfs.8.in | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/man/mkfs.btrfs.8.in b/man/mkfs.btrfs.8.in
index
On Mon, Feb 24, 2014 at 07:29:58AM +, Duncan wrote:
But I'm still seeing these, albeit less often.
Any idea what they could be linked to?
(I have a btrs send/receive going right now, it could hanging
/mnt/btrfs_pool1 in a way that affects smbd, but the array feels ok
otherwise,
On Thu, Feb 20, 2014 at 05:44:14PM -0800, Christoph Hellwig wrote:
- return d_obtain_alias(inode);
+ return d_obtain_alias_root(inode);
Can we call this d_obtain_root or similar, please?
Yes, I like d_obtain_root better, done.
I'll send out the updated series sometime.
--b.
--
To
Extends mkfs.btrfs to support the new par1/2/3/4/5/6 modes to create
filesystem with up to six parities.
Replaces the raid6 code with a new references function able to compute up
to six parities.
Replaces the existing BLOCK_GROUP_RAID5/6 with new PAR1/2/3/4/5/6 ones that
handle up to six parities,
Hi,
A new version of the new RAID library. Finally with *working* btrfs support!
It includes patches for both the kernel and btrfs-progs to add new parity
modes par3, par4, par5 and par6 working similarly at the existing
raid5 and raid6 ones.
The patches apply cleanly to kernel v3.14-rc3 and
Removes the RAID logic now handled in the new raid_gen() and raid_rec() calls
that hide all the details.
Replaces the faila/failb failure indexes with a fail[] vector that keeps
track of up to six failures.
Replaces the existing BLOCK_GROUP_RAID5/6 with new PAR1/2/3/4/5/6 ones that
handle up to
On Mon, Feb 24, 2014 at 01:22:36PM +, Filipe David Manana wrote:
On Mon, Feb 24, 2014 at 12:23 PM, Dave Chinner da...@fromorbit.com wrote:
On Mon, Feb 24, 2014 at 11:56:23AM +, Filipe David Borba Manana wrote:
To avoid repeating detection of fssum presence in many btrfs tests, as
On Mon, Feb 24, 2014 at 5:55 AM, Wang Shilong
wangsl.f...@cn.fujitsu.com wrote:
We found btrfsck will output backrefs mismatch while the filesystem
is defenitely ok.
The problem is that check_block() don't return right value,which
makes btrfsck won't walk all tree blocks thus we don't get a
On Mon, Feb 24, 2014 at 10:22 PM, Dave Chinner da...@fromorbit.com wrote:
On Mon, Feb 24, 2014 at 01:22:36PM +, Filipe David Manana wrote:
On Mon, Feb 24, 2014 at 12:23 PM, Dave Chinner da...@fromorbit.com wrote:
On Mon, Feb 24, 2014 at 11:56:23AM +, Filipe David Borba Manana wrote:
On Mon, Feb 24, 2014 at 11:08:27PM +, Filipe David Manana wrote:
On Mon, Feb 24, 2014 at 10:22 PM, Dave Chinner da...@fromorbit.com wrote:
On Mon, Feb 24, 2014 at 01:22:36PM +, Filipe David Manana wrote:
On Mon, Feb 24, 2014 at 12:23 PM, Dave Chinner da...@fromorbit.com wrote:
diff
Hi Mitch,
On 02/25/2014 07:03 AM, Mitch Harder wrote:
On Mon, Feb 24, 2014 at 5:55 AM, Wang Shilong
wangsl.f...@cn.fujitsu.com wrote:
We found btrfsck will output backrefs mismatch while the filesystem
is defenitely ok.
The problem is that check_block() don't return right value,which
makes
Hi Wang,
Thank you for reviewing my patch.
I ran the test using btrfs progs v0.19(OpenSuse 12.3) previously and got a fail
situation.
I verified v3.12 this morning and it work well as you mentioned.
Althouth the new version doesn't have this problem, I think it would be better
to fix this.
The test 013 couldn't work using some old version btrfs progs
e.g.(btrfs progs v0.19 openSUSE 12.3)because here lacked start.
This patch fix it.
Signed-off-by: Zhang Zhen zhenzhang.zh...@huawei.com
---
tests/btrfs/013 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Thanks Hugo for the heads-up.
I am trying to enhance GParted (http://www.gparted.org/) to better
support btrfs, specifically multi-device ones. GParted displays the
busy status (mounted or not) and the mount point of each partition.
For a single device file system this is easy. Entry in
On Mon, Feb 24, 2014 at 09:35:19AM -0800, Marc MERLIN wrote:
On Mon, Feb 24, 2014 at 07:29:58AM +, Duncan wrote:
But I'm still seeing these, albeit less often.
Any idea what they could be linked to?
(I have a btrs send/receive going right now, it could hanging
/mnt/btrfs_pool1 in
As recently suggested by Dave Chinner, make use of the new function
named _run_btrfs_util_prog() to run the btrfs util program.
Filipe David Borba Manana have cleaned up btrfs/030 and btrfs/034.
I have done the same for the rest ones.
Signed-off-by: Zhang Zhen zhenzhang.zh...@huawei.com
---
I got this during a btrfs send:
BTRFS error (device dm-2): did not find backref in send_root. inode=22672,
offset=524288, disk_byte=1490517954560 found extent=1490517954560
I'll try a scrub when I've finished my backup, but is there anything I
can run on the file I've found from the inode?
On Mon, Feb 24, 2014 at 08:43:44AM +, Duncan wrote:
Hugo Mills posted on Mon, 24 Feb 2014 08:29:38 + as excerpted:
On Mon, Feb 24, 2014 at 06:32:14AM +, Duncan wrote:
This is a known issue. There's patches in the pipeline for 32-bit
userspace on a 64-bit kernel, already.
I was experimenting with the BTRFS_IOC_LOGICAL_INO
BTRFS_IOC_INO_PATHS ioctls and noticed that there are some limits in
the kernel that limit the number or results they return. For example,
for BTRFS_IOC_LOGICAL_INO, the structure that will hold the results
can be up to 65536 bytes. Are there any
Fix corporate name for copyright.
Signed-off-by: Hidetoshi Seto seto.hideto...@jp.fujitsu.com
---
fs/btrfs/delayed-inode.c |2 +-
fs/btrfs/delayed-inode.h |2 +-
fs/btrfs/math.h |2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/btrfs/delayed-inode.c
Hi Marc,
This seems a regression which has been fixed by the following
commit(only pushed into btrfs-next):
https://git.kernel.org/cgit/linux/kernel/git/josef/btrfs-next.git/commit/?id=1334bebe71bebbca47b3b92f25511ea980fdeab8
Thanks,
Wang
On 02/25/2014 02:36 PM, Marc MERLIN wrote:
I got this
46 matches
Mail list logo
