On Thu, Jul 9, 2015 at 8:20 AM, james harvey wrote:
> Request for new btrfs subvolume subcommand:
>
> clone or fork [-i []
>Create a subvolume in , which is a clone or fork of source.
>If is not given, subvolume will be created in the
> current directory.
>Options
>-i
>
OK yet another btrfs-convert bug. This one is easier to reproduce than
the others, does not damage the file system (still mounts OK) but the
oops is a hard panic. ssh and even the virt-manager console dies
instantly, but virsh console captured a lot of call traces and are
attached to the bug report
On Thu, Jun 25, 2015 at 8:08 PM, Qu Wenruo wrote:
> A quite code search leads me to inline extent.
>
> So, if you still have the original ext* image,
> would you please try revert to ext* and then convert it to btrfs again?
>
> But this time, please convert with --no-inline option, and see if thi
I've filed a bug for the btrfs check and btrfs-image crashing/failure
I'm getting. They may be unrelated but I filed them as one bug here.
https://bugzilla.kernel.org/show_bug.cgi?id=101221
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a me
Request for new btrfs subvolume subcommand:
clone or fork [-i []
Create a subvolume in , which is a clone or fork of source.
If is not given, subvolume will be created in the
current directory.
Options
-i
Add the newly created subvolume to a qgroup. This option can be
given
Request for new btrfs subvolume subcommand:
tree
Display a depth indented listing of subvolumes present in the
filesystem .
---or---
list ... --tree ...
...
-tree
display subvolumes in a depth indented listing.
Would (I think):
* Display each top-level subvolume
* Recursively di
--
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 http://vger.kernel.org/majordomo-info.html
On Wed, Jul 8, 2015 at 1:38 PM, Николай Овчинников wrote:
> What about btrfsck and btrfs-image errors?
btrfs check and btrfs-image both crash, which I consider as a separate
bug. And the crash doesn't produce useful info so I think it's a case
where I need to include either some gdb or valgrind i
This is similar to previously reported ext4->btrfs convert success,
but then failure on subsequent balance. But this is a different kernel
version and totally different call traces, so I've filed it with a
separate bug report and email thread.
Kernel 4.2.0rc1
Btrfs-progs 4.1
New ext4 file system
Noah Massey posted on Wed, 08 Jul 2015 16:02:04 -0400 as excerpted:
> Standard disclaimer: Not a developer, just a user.
Same here. =:^)
> The 1.5 GB ISO on a fresh ext4 system made me think of
> http://thread.gmane.org/gmane.comp.file-systems.btrfs/36955 (ext4
> extents over 1 GB causing ENOSPC
2015-07-09 2:32 GMT+03:00 Duncan <1i5t5.dun...@cox.net>:
> Николай Овчинников posted
> on Wed, 08 Jul 2015 22:38:20 +0300 as excerpted:
>
>> 2015-07-08 16:56 GMT+03:00 Chris Murphy :
>>> I've reproduced this bug with a brand new ext4 system, converted with
>>> btrfs-progs 4.1 and a 4.1 kernel. The
Николай Овчинников posted
on Wed, 08 Jul 2015 22:38:20 +0300 as excerpted:
[Rearranged to standard quote, reply-in-context, format. It makes
replying and following replies on mailing lists FAR easier.]
> 2015-07-08 16:56 GMT+03:00 Chris Murphy :
>> I've reproduced this bug with a brand new ext4
Basically I wouldn't trust the drive that's already showing signs of
failure to survive a dd. It isn't completely full, so the recover is
less load. That's just the way I see it. But I see your point of
trying to get drive images now to hedge against failures.
Unfortunately those errors are ove
Hello Donald,
thanks for your reply. I appreciate your help.
> I would use recover to get the data if at all possible, then you can
experiment with try to fix the degraded condition live. If you have
any chance of getting data from the pool, you reduce that chance every
time you make a change.
Looks like my case.
I also have some files over 1Gb ans skip defrag before balance.
2015-07-08 23:02 GMT+03:00 Noah Massey :
> On Wed, Jul 8, 2015 at 10:01 AM, Chris Murphy wrote:
>> The short version: btrfs convert and subsequent balance will eat an
>> ext4 file system. I've reproduced this 6 f
On Wed, Jul 8, 2015 at 10:01 AM, Chris Murphy wrote:
> The short version: btrfs convert and subsequent balance will eat an
> ext4 file system. I've reproduced this 6 for 6 times with both kernel
> 4.1 and 4.2rc1, but I get different back traces for the two kernels.
>
> Kernel 4.1.0
> Btrfs-progs 4
What about btrfsck and btrfs-image errors?
2015-07-08 16:56 GMT+03:00 Chris Murphy :
> I've reproduced this bug with a brand new ext4 system, converted with
> btrfs-progs 4.1 and a 4.1 kernel. The conversion is OK. And btrfs
> check is ok after conversion, after removing the ext2_saved snapshot,
>
I wouldn't use dd.
I would use recover to get the data if at all possible, then you can
experiment with try to fix the degraded condition live. If you have
any chance of getting data from the pool, you reduce that chance every
time you make a change.
If btrfs did the balance like you said, it wo
Hello,
yes, I will check the cables, thanks for the hint.
Before trying to recover the data, I would like to save the status quo.
I have two new drives? Is it advisable to dd-copy the data on the new
drives and then to try to recover?
I am asking, because I suppose that dd will also copy the
I am a high school student trying to become familiar with
Linux kernel development. The btrfs documentation in
Documentation/filesystems had a few typos and errors in
whitespace. This patch corrects both of these.
This is a resend of an earlier patch with corrected patchfile.
Signed-off-by: Danie
On Wed, 08 Jul 2015 08:22:20 -0700
Daniel Grimshaw wrote:
> I am a high school student trying to become familiar with Linux kernel
> development.
That's great!
> The btrfs documentation in Documentation/filesystems had a
> few typos and errors in whitespace. This patch corrects both of these.
I am a high school student trying to become familiar with Linux kernel
development. The btrfs documentation in Documentation/filesystems had a few
typos and errors in whitespace. This patch corrects both of these.
Signed-off-by: Daniel Grimshaw
---
diff --git a/Documentation/filesystems/btrfs.
The short version: btrfs convert and subsequent balance will eat an
ext4 file system. I've reproduced this 6 for 6 times with both kernel
4.1 and 4.2rc1, but I get different back traces for the two kernels.
Kernel 4.1.0
Btrfs-progs 4.1
New ext4 file system populated with several thousand files (F
I've reproduced this bug with a brand new ext4 system, converted with
btrfs-progs 4.1 and a 4.1 kernel. The conversion is OK. And btrfs
check is ok after conversion, after removing the ext2_saved snapshot,
and after defrag. The implosion happens on balance and the fs goes
read only.
https://bugzil
Liu Bo wrote on 2015/07/08 17:03 +0800:
On Thu, Oct 30, 2014 at 04:52:31PM +0800, Qu Wenruo wrote:
The following lockdep warning is triggered during xfstests:
[ 1702.980872] =
[ 1702.981181] [ INFO: possible irq lock inversion dependency
On Thu, Oct 30, 2014 at 04:52:31PM +0800, Qu Wenruo wrote:
> The following lockdep warning is triggered during xfstests:
>
> [ 1702.980872] =
> [ 1702.981181] [ INFO: possible irq lock inversion dependency detected ]
> [ 1702.981482] 3.18.0-r
This patch adds the support to show seed device on the btrfs sysfs.
This is a revamped version of the previously single patch 6/6, and plus
incorporates David suggestion to add seed fsid under the 'seed' kobject.
Since this adds new patches and to bring in seed kobject it needed
quite a lot of rev
Signed-off-by: Anand Jain
---
fs/btrfs/dev-replace.c | 2 +-
fs/btrfs/sysfs.c | 4 ++--
fs/btrfs/sysfs.h | 2 +-
fs/btrfs/volumes.c | 2 +-
4 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/fs/btrfs/dev-replace.c b/fs/btrfs/dev-replace.c
index 862fbc2..f7c390b 100644
Signed-off-by: Anand Jain
---
fs/btrfs/dev-replace.c | 2 +-
fs/btrfs/sysfs.c | 6 +++---
fs/btrfs/sysfs.h | 2 +-
fs/btrfs/volumes.c | 6 +++---
4 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/fs/btrfs/dev-replace.c b/fs/btrfs/dev-replace.c
index f7c390b..31e0145 1
Signed-off-by: Anand Jain
---
fs/btrfs/sysfs.c | 36 ++--
fs/btrfs/volumes.c | 2 +-
fs/btrfs/volumes.h | 2 +-
3 files changed, 20 insertions(+), 20 deletions(-)
diff --git a/fs/btrfs/sysfs.c b/fs/btrfs/sysfs.c
index 52319d1..e0ac859 100644
--- a/fs/btrfs/sys
Signed-off-by: Anand Jain
---
fs/btrfs/ctree.h | 2 +-
fs/btrfs/disk-io.c | 2 +-
fs/btrfs/sysfs.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
index 80a9aef..b6b2226 100644
--- a/fs/btrfs/ctree.h
+++ b/fs/btrfs/ctree.h
@@ -4007,7
Signed-off-by: Anand Jain
---
fs/btrfs/ctree.h | 2 +-
fs/btrfs/disk-io.c | 4 ++--
fs/btrfs/sysfs.c | 4 ++--
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
index b6b2226..eed1127 100644
--- a/fs/btrfs/ctree.h
+++ b/fs/btrfs/ctree.h
@@ -400
This adds an enhancement to show the seed fsid and its devices
on the btrfs sysfs.
The way sprouting handles fs_devices:
clone seed fs_devices and add to the fs_uuids
mem copy seed fs_devices and assign to fs_devices->seed (move dev_list)
evacuate seed fs_devices contents to hold
33 matches
Mail list logo
