similar to: mountinfo discrepancy, subvol vs subvolid

Hello Joenes, below you find the output. I did not shorten it by tmpfs and the docker related entries. Are you working on fixing the Issue I described? Regards, Hendrik df -TPh Dateisystem Typ Gr??e Benutzt Verf. Verw%

Although for most time, int is enough for subvolid, we should ensure safety in theory. Signed-off-by: Wang Shilong <wangsl.fnst@cn.fujitsu.com> Reviewed-by: Miao Xie <miaox@cn.fujitsu.com> --- fs/btrfs/super.c | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c index cc00295..d82391d 100644 --- a/fs/btrfs/super.c

HI all, >----Messaggio originale---- >Da: chris.mason@fusionio.com >Data: 20/06/2012 1.49 >A: "H. Peter Anvin"<hpa@zytor.com> >Cc: "linux-btrfs@vger.kernel.org"<linux-btrfs@vger.kernel.org> >Ogg: Re: Subvolumes and /proc/self/mountinfo > >> b. Are there better ways (walking the tree using BTRFS_IOC_TREE_SEARCH?) >> to accomplish

I''ve been running BTRFS for a while testing out various stuff, and I''ve found it to be quite stable (although reading this list makes me realize how much activity there really is).. I just hit my first bump in the road, and I wondered if someone could give me a hint how I can gather enough information to be useful here. Basically, the filesystem I''m running is a 2 disk

On Fri, Oct 10, Olaf Hering wrote: > Is btrfs subvol support failing just for me? This is an old thread, and it seems the underlying bug is not fixed because guestfs takes the wrong approach, IMO. >From how I understand btrfs, it has the concept of subvolumes. Each one is an entry point for a separate filesystem. In addition to that it has a default subvol which is used if no specific

This fixes the issue I had come across with the default subvolume not being set/used on btrfs when isntalling via `extlinux --install /boot/syslinux`. Signed-off-by: Jordan Beaver <jordan at beaveris.me> --- extlinux/main.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/extlinux/main.c b/extlinux/main.c index 09740bd..c3d9612 100644 --- a/extlinux/main.c +++ b/extlinux/main.c @@

Hello Hendrik Can you help input 2 commands 'mount' and 'df -TPh' on OMV, and post the output to us, thank you. -- Regards, Jones Syue | ??? QNAP Systems, Inc.

On Tue, Dec 9, 2014 at 5:45 AM, Jordan Beaver <jordan at beaveris.me> wrote: > This fixes the issue I had come across with the default subvolume not being > set/used on btrfs when isntalling via `extlinux --install /boot/syslinux`. > > Signed-off-by: Jordan Beaver <jordan at beaveris.me> > --- > extlinux/main.c | 3 +++ > 1 file changed, 3 insertions(+) > >

Hi, a recent Ubuntu upgrade killed my system. Luckily I had done a btrfs snapshot before, so I set the particular subvolume as default using # btrfs subvolume set-default 261 /mnt from a rescue system and was back up in no time. I then mounted the original volume with subvolid=0 and repaired it. So far so good. However, I fail to set the default volume back to the original. # btrfs subvolume

Is btrfs subvol support failing just for me? Looks like nothing adds the required '@/' string. virt-ls uses the first variant of the command: ><rescue> mount -vo subvol=var/spool,ro /dev/sda2 /sysroot/ [ 113.852047] BTRFS info (device sda2): disk space caching is enabled [ 113.852869] BTRFS: has skinny extents mount: mount(2) failed: No such file or directory ><rescue>

On Mon, 2003-12-01 at 13:52, Melanie wrote: > True - in that case, another fix ist called for, but it's just as simple: > > diff -b -B -r -u -P --exclude-from=ignore ../icecast/src/source.c > ./src/source.c--- ../icecast/src/source.c Mon Dec 1 14:49:52 2003 > +++ ./src/source.c Mon Dec 1 14:50:56 2003 > @@ -72,7 +72,7 @@ > src->yp_public = 0; > >

Hi, this patch enables the use of time stamps in dump file names: diff -ur icecast-2.0.1/src/source.c icecast-2.0.1.scram/src/source.c --- icecast-2.0.1/src/source.c Wed May 12 17:55:30 2004 +++ icecast-2.0.1.scram/src/source.c Wed Jun 2 23:17:29 2004 @@ -50,6 +50,16 @@ http_parser_t *parser, const char *mount, format_type_t type, mount_proxy *mountinfo) { + char buffer[PATH_MAX]; +

Hi, this patch enables the use of time stamps in dump file names: diff -ur icecast-2.0.1/src/source.c icecast-2.0.1.scram/src/source.c --- icecast-2.0.1/src/source.c Wed May 12 17:55:30 2004 +++ icecast-2.0.1.scram/src/source.c Wed Jun 2 23:17:29 2004 @@ -50,6 +50,16 @@ http_parser_t *parser, const char *mount, format_type_t type, mount_proxy *mountinfo) { + char buffer[PATH_MAX]; +

So when I added the clear_cache option I screwed up and took the break out of the space_cache case statement, so whenever you mount with space_cache you also get clear_cache, which does you no good if you say set space_cache in fstab so it always gets set. This patch adds the break back in properly. Thanks, Signed-off-by: Josef Bacik <josef@redhat.com> --- fs/btrfs/super.c | 1 + 1

True - in that case, another fix ist called for, but it's just as simple: diff -b -B -r -u -P --exclude-from=ignore ../icecast/src/source.c ./src/source.c--- ../icecast/src/source.c Mon Dec 1 14:49:52 2003 +++ ./src/source.c Mon Dec 1 14:50:56 2003 @@ -72,7 +72,7 @@ src->yp_public = 0; if(mountinfo != NULL) { - src->fallback_mount = mountinfo->fallback_mount;

On Wed, Jan 15, 2014 at 3:26 AM, Johann Obermayr <johann.obermayr at sigmatek.at> wrote: > Am 15.01.2014 04:57, schrieb Gene Cumm: > >> On Tue, Jan 14, 2014 at 10:50 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> >>> On Tue, Jan 14, 2014 at 9:28 AM, Johann Obermayr >>> <johann.obermayr at sigmatek.at> wrote: >>>>

Am 15.01.2014 04:57, schrieb Gene Cumm: > On Tue, Jan 14, 2014 at 10:50 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Tue, Jan 14, 2014 at 9:28 AM, Johann Obermayr >> <johann.obermayr at sigmatek.at> wrote: >>> Hello, >>> >>> i'm using version 4.07. >>> On my computer extlinux does not work. >>> after debugging, i

Here's a hack to the icecast2 source to make icecast listen to older clients that don't supply a username when negotiating a stream (like xmms-liveice) The Warning is a standard disclaimer -Pete pjf@cape.com http://vsa.cape.com/~pjf http://www.mraudrey.net icecast2 - letme-in hack MRU 20040124 V0.3 pjf@cape.com Pete Flaherty This hack is for the connections.c source file, and will

Attached you will find a patch against the icecast-2.0.0 released source code which implements listener time limits on a global or mount-specific scope. Two new configuration elements are added with this patch: client-time-limit: This is a GLOBAL directive which covers all connections. Its value is given in seconds. So for example, if you want to limit all listeners on all mount points to 1

libvirt version: 3.4.0 architecture: x86_64 ubuntu16.04-server hypervisor: kvm,qemu When migrate vm, I encounter error: "Migrate VM virt21 failed unsupported configuration: Unable to find security driver for model apparmor" but two host are same environment.before this error, migrate can be success. the source host seclabel configure is this : <seclabel type='dynamic'