On Tue, Sep 04, 2018 at 07:55:00PM -0600, Chris Murphy wrote:
> https://rwmj.wordpress.com/2018/09/04/nbdkit-as-a-flexible-alternative-to-loopback-mounts/
>
> This is a pretty cool writeup. I can vouch Btrfs will format mount,
> write to, scrub, and btrfs check works on an 8EiB (virtual) disk.
>
>
On Sun, May 05, 2013 at 11:26:17AM +, Fedora Rawhide Report wrote:
> [libguestfs]
> 1:libguestfs-1.21.36-1.fc20.i686 requires libbtrfs.so.0
> 1:libguestfs-1.21.36-1.fc20.x86_64 requires libbtrfs.so.0()(64bit)
I've started a rebuild of libguestfs which should fix this.
Is there any
In the original version of "btrfs-progs: libify some parts of
btrfs-progs" by Mark Fasheh, the soname field of the internal libbtrfs
library was set to "libbtrfs.so.1". This doesn't match the filename
of the library (libbtrfs.so.0.1) which is unusual.
However in the version which went upstream, t
From: "Richard W.M. Jones"
Signed-off-by: Richard W.M. Jones
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 9c195b3..d2c2e28 100644
--- a/Makefile
+++ b/Makefile
@@ -93,7 +93,7 @@ version.h:
$(libs_shared): $(libbtr
libguestfs could really use structured output from more of the command
line tools. Particularly:
- all the ext4 tools
- all the xfs tools
- all the btrfs tools
- parted
and more. See also:
https://github.com/libguestfs/libguestfs/tree/master/daemon
A dbus service would not be useful.
I'm tracking this bug here:
https://bugzilla.redhat.com/show_bug.cgi?id=863978
Since approx. last week I'm seeing lots of failures in btrfs. The
common factor seems to be that the filesystem is created (mkfs.btrfs
/dev/sda1) and then it is immediately used -- eg. mounted or some
btrfs subtool
On Mon, Oct 08, 2012 at 10:27:57AM -0400, Chris Mason wrote:
> On Mon, Oct 08, 2012 at 08:16:42AM -0600, Richard W.M. Jones wrote:
> >
> > I'm tracking this bug here:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=863978
> >
> > Since approx. la
On Mon, Oct 08, 2012 at 11:04:19AM -0400, Chris Mason wrote:
> On Mon, Oct 08, 2012 at 08:57:30AM -0600, Richard W.M. Jones wrote:
> > On Mon, Oct 08, 2012 at 10:27:57AM -0400, Chris Mason wrote:
> > > On Mon, Oct 08, 2012 at 08:16:42AM -0600, Richard W.M. Jones wrote:
&g
On Mon, Oct 08, 2012 at 06:42:27PM +0200, David Sterba wrote:
> On Mon, Oct 08, 2012 at 04:15:14PM +0100, Richard W.M. Jones wrote:
> > Unfortunately I'm struggling to reproduce this outside of our build
> > system (Koji). I will keep you informed if I do manage to repr
On Mon, Oct 08, 2012 at 04:15:14PM +0100, Richard W.M. Jones wrote:
> On Mon, Oct 08, 2012 at 11:04:19AM -0400, Chris Mason wrote:
> > On Mon, Oct 08, 2012 at 08:57:30AM -0600, Richard W.M. Jones wrote:
> > > On Mon, Oct 08, 2012 at 10:27:57AM -0400, Chris Mason wrote:
> >
On Mon, Oct 08, 2012 at 08:00:51PM -0400, Chris Mason wrote:
> On Mon, Oct 08, 2012 at 03:22:30PM -0600, Richard W.M. Jones wrote:
> >
> > I have now reproduced this bug locally.
> >
> > Adding sync() + fsync of each /dev/sd* device after the mkfs command
> &g
On Tue, Oct 09, 2012 at 08:20:02AM +0100, Richard W.M. Jones wrote:
> On Mon, Oct 08, 2012 at 08:00:51PM -0400, Chris Mason wrote:
> > On Mon, Oct 08, 2012 at 03:22:30PM -0600, Richard W.M. Jones wrote:
> > >
> > > I have now reproduced this bug locally.
> > >
On Tue, Oct 09, 2012 at 11:16:57AM +0200, David Sterba wrote:
> On Tue, Oct 09, 2012 at 08:20:02AM +0100, Richard W.M. Jones wrote:
> > On my local machine, I'm reproducing this with what Fedora calls
> > 3.7.0-0.rc0.git2.4.fc19.x86_64 (note I found an unrelated but very
>
On Mon, Oct 08, 2012 at 10:22:30PM +0100, Richard W.M. Jones wrote:
> Adding sync() + fsync of each /dev/sd* device after the mkfs command
> does appear to fix the problem.
>
> However it's a little bit difficult to know for sure because I might
> just be changing the timing
On Wed, Oct 10, 2012 at 08:38:08AM -0400, Chris Mason wrote:
> On Tue, Oct 09, 2012 at 03:00:12AM -0600, David Sterba wrote:
> > On Tue, Oct 09, 2012 at 08:33:57AM +0100, Richard W.M. Jones wrote:
> > > On Tue, Oct 09, 2012 at 08:20:02AM +0100, Richard W.M. Jones wrote:
>
On Wed, Oct 10, 2012 at 03:41:13PM -0400, Chris Mason wrote:
> On Wed, Oct 10, 2012 at 01:38:53PM -0600, Richard W.M. Jones wrote:
> > On Wed, Oct 10, 2012 at 08:38:08AM -0400, Chris Mason wrote:
> > > On Tue, Oct 09, 2012 at 03:00:12AM -0600, David Sterba wrote:
> > > &
Well the bad news is that the bug happened again overnight, even
though we were definitely using btrfs-progs with the 6eba90029 patch
added, _and_ it was doing a sync + fsync between the mkfs and the
mount.
Here is the log:
modprobe btrfs
[ 15.716610] Btrfs loaded
grep ^[[:space:]]*btrfs$ /proc
I don't have time to implement this right now, so I'm just posting
this as a suggestion/request ...
It would be really helpful if the btrfs tools had a machine-readable
output.
Libguestfs parses btrfs tools output in a number of places, eg:
https://github.com/libguestfs/libguestfs/blob/master/dae
On Mon, May 16, 2016 at 02:21:07PM +0200, Martin Steigerwald wrote:
> Hello Richard,
>
> On Montag, 16. Mai 2016 13:14:56 CEST Richard W.M. Jones wrote:
> > I don't have time to implement this right now, so I'm just posting
> > this as a suggestion/request ...
>
As I said I don't have any particular favourite format. However I'll
just point you to the code that qemu uses (basically open-coding) to
write json:
http://git.qemu.org/?p=qemu.git;a=blob;f=qobject/qjson.c;h=ef160d2119eb18aa917b71b40e37d54880b1ac7f;hb=HEAD#l83
Hopefully this is useful as a data
On Thu, Oct 11, 2012 at 07:26:28AM -0400, Chris Mason wrote:
> On Thu, Oct 11, 2012 at 01:28:21AM -0600, Richard W.M. Jones wrote:
> > Well the bad news is that the bug happened again overnight, even
> > though we were definitely using btrfs-progs with the 6eba90029 patch
> >
Btrfs has been broken for me for ages. I first reported it on this
list 5 months ago[1]. Below is a very simple reproducer that anyone
can run.
*NB* before you run this, adjust /dev/sda & /dev/sda1 to point to an
unused block device!
-
On Tue, Feb 12, 2013 at 02:16:37PM -0500, Josef Bacik wrote:
> On Tue, Feb 12, 2013 at 11:54:49AM -0700, Richard W.M. Jones wrote:
> > Btrfs has been broken for me for ages. I first reported it on this
> > list 5 months ago[1]. Below is a very simple reproducer that any
On Tue, Feb 12, 2013 at 11:44:56AM -0800, Zach Brown wrote:
> On Tue, Feb 12, 2013 at 06:54:49PM +0000, Richard W.M. Jones wrote:
> > Btrfs has been broken for me for ages. I first reported it on this
> > list 5 months ago[1]. Below is a very simple reproducer that anyone
> &
On Tue, Feb 12, 2013 at 04:42:25PM -0500, Chris Mason wrote:
> On Tue, Feb 12, 2013 at 02:05:35PM -0700, Richard W.M. Jones wrote:
> >
> > Yes, this is inside a very recent KVM (qemu 1.3.0), using virtio-scsi
> > as the backing disk.
>
> Ok, can you please run this
On Wed, Feb 13, 2013 at 11:00:33AM +, Richard W.M. Jones wrote:
> Will try the btrfsprogs patch next.
I applied this patch:
https://git.kernel.org/?p=linux/kernel/git/mason/btrfs-progs.git;a=commitdiff_plain;h=8fe354744cd7b5c4f7a3314dcdbb5095192a032f
to the version of btrfs-progs in Fed
26 matches
Mail list logo
