search for: subvolid

...ve me a hint how I can gather enough information to be useful here. Basically, the filesystem I''m running is a 2 disk stripe, with mirrored metadata.. I have default subvolume set, and I''m using 2 subvolumes. I have created a few snapshots of those subvolumes by mounting with -o subvolid=0 and creating snapshots of the mounted subvolumes. Recently (I think it started when I updated from .38rc1 to .38rc5 but that could be coincidental)... when I mount subvolid=0, if I do a ''ls'' of that mount point, the filesystem hangs, and the system becomes unusable. Otherwise...

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.

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...

When mounting a subvolume by name, mountinfo shows the name of the subvolume. When mounting a subvolume using subvolid it does not. Seems like a problem when trying to determine what is mounted. -o subvol=<name> # cat /proc/self/mountinfo | grep vda 43 34 0:29 /home /home rw,relatime shared:29 - btrfs /dev/vda1 rw,seclabel,space_cache 44 34 0:29 /boot /boot rw,relatime shared:30 - btrfs /dev/vda1 rw,seclab...

...433cd-993d-4af7-9114-fb761bccdbbf:srv/dev-disk-by-label-Big5:srv/dev-disk-by-id-ata-ST4000DM005-2DP166_ZDH26KL5-part1 on /export/Daten type fuse.mergerfs (rw,relatime,user_id=0,group_id=0,allow_other) /dev/sde3 on /srv/dev-disk-by-label-DockerImages type btrfs (rw,noatime,ssd,discard,space_cache,subvolid=5,subvol=/) /dev/sde3 on /sharedfolders/docker_dir type btrfs (rw,noatime,ssd,discard,space_cache,subvolid=5,subvol=/Docker) /dev/sdg on /srv/dev-disk-by-id-ata-ST3000DM001-9YN166_Z1F0GY9A type ext4 (rw,noexec,relatime,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group) /dev/sdb1 on /srv/d...

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 set-default 0 / apparently does nothing, I don''t get an error but I''m still on the snapshot after reboot. Currently I''m working around this adding rootfl...

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(+) > >

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 @@

NFS needs a unique identifier for a filesystem to be able to export it. This can be set by the admin (fsid= in /etc/exports) but that is a hassle and it is best to set it automatically. nfs-utils currently uses the UUID returned by libblkid if that works, or the fsid returned by statfs64 if libblkid finds nothings and fsid is non-zero. Otherwise it uses device major/minor. This

As of the latest updates to anaconda and grub2 for Fedora 18, it is now possible to install with /boot as a btrfs subvolume. The way that grub2 is handling this is the "reach down" to the files it needs as if the subvolume was a directory. Is this OK? At this point I am not worried about snapshots or any other complexities. If the subvolume name is known. should grub2 be able to

I've just tried putting usr in a subvol. Installation proceeds normally, no errors, but I'm dropped to a dracut prompt which indicates mount of /usr failed. dmesg follows: [ 14.025215] systemd[1]: Starting dracut initqueue hook... [ 14.077890] Btrfs loaded [ 14.129987] device label fedora_f18v devid 1 transid 31 /dev/sda1 [ 14.313607] device label fedora_f18v devid 1 transid 31

Setting subvolume/snapshot readonly has been missing for a long time. With this patch, we can set a subvolume/snapshot readonly via: o btrfs subvolume set-ro <path> Signed-off-by: Liu Bo <liubo2009@cn.fujitsu.com> --- cmds-subvolume.c | 40 ++++++++++++++++++++++++++++++++++++++++ ioctl.h | 7 +++++++ 2 files changed, 47 insertions(+), 0 deletions(-) diff --git

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>

I thought I would try btrfs on a new installation of f14. yes, I know its experimental but stable so it seemed to be a good time to try it. I am not sure if I have missed something out of all my searching but am I correct in thinking that currently: I. it is not possible to boot from a snapshot of the operating system and, in particular, the yum snapshots cannot be used for

Hi! With 3.2-rc4 (probably earlier), Ext4 seems to remember what areas it trimmed: merkaba:~> fstrim -v /boot /boot: 224657408 bytes were trimmed merkaba:~> fstrim -v /boot /boot: 0 bytes were trimmed But BTRFS does not: merkaba:~> fstrim -v / /: 4431613952 bytes were trimmed merkaba:~> fstrim -v / /: 4341846016 bytes were trimmed Is it planned to add this feature to BTRFS

...che,clear_cache 7) I unmount everything and attempt to boot the USB disk. I receive "Failed to load ldlinux.c32" on the console. extlinux: 6.04 (bf6db5b4) Note: I am able to successfully boot a btrfs subvolume if I place the extlinux.conf at / when I mount the disk with "mount -o subvolid=0 /dev/sdd1 /mnt". I "cd /mnt" and "mv root/ldlinux.c32|extlinux.conf|vmlinuz-5.2.0-2-686-pae|initrd.img-5.2.0-2-686-pae" files to /mnt. One special problem with this setup is that symbolic links are not followed. For example, if I symlink /mnt/vmlinuz -> /mnt/root/boot/...

...e,clear_cache 7) I unmount everything and attempt to boot the USB disk. I receive "Failed to load ldlinux.c32" on the console. extlinux: 6.04 (bf6db5b4) Note: I am able to successfully boot a btrfs subvolume if I place the extlinux.conf at / when I mount the disk with "mount -o subvolid=0 /dev/sdd1 /mnt". I "cd /mnt" and "mv root/ldlinux.c32|extlinux.conf|vmlinuz-5.2.0-2-686-pae|initrd.img-5.2.0-2-686-pae" files to /mnt. One special problem with this setup is that symbolic links are not followed. For example, if I symlink /mnt/vmlinuz -> /mnt/root/b...

...e,clear_cache 7) I unmount everything and attempt to boot the USB disk. I receive "Failed to load ldlinux.c32" on the console. extlinux: 6.04 (bf6db5b4) Note: I am able to successfully boot a btrfs subvolume if I place the extlinux.conf at / when I mount the disk with "mount -o subvolid=0 /dev/sdd1 /mnt". I "cd /mnt" and "mv root/ldlinux.c32|extlinux.conf|vmlinuz-5.2.0-2-686-pae|initrd.img-5.2.0-2-686-pae" files to /mnt. One special problem with this setup is that symbolic links are not followed. For example, if I symlink /mnt/vmlinuz -> /mnt/root/b...

...ends up somewhere. Then it tries to make sense of the other subvolumes based on info from a /etc/fstab, which may or may not exist. This looks like the wrong approach. Shouldnt it instead handle the whole thing as a container, just as it does for an individual disk? First do something like mount subvolid=0, poke around there and collect the items (sub list -a). Then use all this info to see which one might be one of the many root filesystems? Olaf

In the latest btrfs tools from git it''s a typo: ierdnac-hp ~ # btrfs|grep dafault btrfs subvolume get-dafault <path> btrfs subvolume set-dafault <subvolid> <path> ierdnac-hp ~ # Andrei -- Andrei Popa NOC Manager - Nextgen Communications 0760 683 280