search for: fsid

...2009 ... virtual-206 kernel: [ 121.409129] ------------[ cut here ]------------ + umount /mnt Segmentation fault + set +x + mount -t btrfs /dev/disk/by-path/ccw-0.0.3321 /mnt ---- ## DMESG Output: ---- [ 32.240137] eth0: no IPv6 routers present [ 115.488507] Btrfs loaded [ 115.866519] device fsid 29b83b8d393a4dc1-8cb6f13d4c8056c9 devid 1 transid 5 /dev/disk/by-path/ccw-0.0.3320 [ 115.915710] device fsid 29b83b8d393a4dc1-8cb6f13d4c8056c9 devid 2 transid 5 /dev/disk/by-path/ccw-0.0.3321 [ 115.946999] device fsid 29b83b8d393a4dc1-8cb6f13d4c8056c9 devid 3 transid 5 /dev/disk/by-path/ccw-0.0.3...

Hi, the $subj warning appears sometimes in syslog, in my case when xfstests/209 runs looped. The minimal reproducer is looped mkfs+mount. The message comes from disk-io.c btree_readpage_end_io_hook(): 581 if (check_tree_block_fsid(root, eb)) { 582 printk_ratelimited(KERN_INFO "btrfs bad fsid on block %llu\n", 583 (unsigned long long)eb->start); 584 ret = -EIO; 585 goto err; 586 } relevant syslog messages: [420367.199710] dev...

What is the purpose of FSIDs? I am exporting 30 volumes via NFS. Do I need a FSID option? TIA

Hi, I would like to use the NFSv4 ability to create a "root" filesystem with fsid=0, so that I don't have to refer to the whole path of the exported filesystem when I mount it. However I do *not* want this root filesystem to be mountable by any host. Is that possible and how? E.g Filesystem: /exports/data1 /exports/data2 /exports/data3 /etc/exports: /export...

From: anand jain <anand.jain@oracle.com> Anand Jain (1): [RFC] Add btrfs autosnap feature Makefile | 6 +- autosnap.c | 1553 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ autosnap.h | 81 +++ btrfs-list.c | 140 +++++- btrfs.c | 46 ++- btrfs_cmds.c | 186 +++++++- btrfs_cmds.h | 3 +- scrub.c | 1 + 8 files changed, 1982 insertions(+), 34

...been experimenting exporting btrfs subvolumes over nfs. Main subvolume is filesys1 mounted at /filesys1. Below this is subvolume base, user1 is in base and documents is in user1. documents is mounted at /documents. /etc/exports is: /filesys1/base/user1 172.16.0.0/24(rw,no_acl,no_root_squash,fsid=0) /filesys1/user1-snapshot 172.16.0.0/24(rw,no_acl,no_root_squash,fsid=0) /documents 172.16.0.0/24(rw,no_acl,no_root_squash,fsid=0) On the client machine I mount user1 as /mnt/user and all data from user is present. I can also umount /mnt/usr and mount /documents as /mnt/documents and...

This adds ioctl BTRFS_IOC_GET_FSIDS which reads the fs info through the btrfs-control Signed-off-by: Anand Jain <anand.jain@oracle.com> --- fs/btrfs/super.c | 47 ++++++++++++++++++++++++++++++++++++++----- fs/btrfs/volumes.c | 33 ++++++++++++++++++++++++++++++ fs/btrfs/volumes.h | 2 + incl...

...uster to communicate to the NFS active server. 3. The active node fails over to the secondary node in the cluster. 4. The NFS clients can no longer access the same major minor number for NFS shares. Does anyone know how ZFS fixes this problem. I read something on NFSv4 in Linux that has the "fsid" option of mount that allows you to set the device name instead of the major/minor number. Does Solaris 10 have anything like this? Thanks, ljs This message posted from opensolaris.org

Frank Thommen wrote: > > I would like to use the NFSv4 ability to create a "root" filesystem with > fsid=0, so that I don't have to refer to the whole path of the exported > filesystem when I mount it.? However I do *not* want this root > filesystem to be mountable by any host.? Is that possible and how? > > E.g > Filesystem: > ? /exports/data1 > ? /exports/data2 > ? /e...

...into (on CentOS 6 anyways), and then only if you export subdirectories in the XFS file system, if you just export the root of it, you won't have any issues. if you are exporting subdirectories (something I find Windows admins like to do), then you have to specify a locally unique integer fsid on each export. I just use fsid=1, fsid=2, ... -- john r pierce, recycling bits in santa cruz

...hots seems to be confusing /proc/mounts After mounting a snapshot of an original filesystem, the devicename of the original filesystem is overwritten with that of the snapshot in /proc/mounts. Steps to reproduce: arnd@kallisto:/mnt$ sudo mount /dev/vg0/original /mnt/original [ 107.041432] device fsid 5c3e8ca2-da56-4ade-9fef-103a6a8a70c2 devid 1 transid 4 /dev/mapper/vg0-original [ 107.044691] btrfs: no dev_stats entry found for device /dev/mapper/vg0-original (devid 1) (OK on first mount after mkfs) arnd@kallisto:/mnt$ cat /proc/mounts | grep /mnt /dev/mapper/vg0-original /mnt/original btrfs...

Well, we got it working. However, the issue we're now worried about is users creating files and subdirectories. Do we need to worry, and if so, is there some way to reserve inodes < 32k table, other than creating tens of thousands of dummy files now? We don't want, a year or two down the road, for this system to be running, and suddenly everything's broken, because all lower inodes

This is the next patch series for scrub userland tools. Change log v1->v2: - commands now reachable as "btrfs scrub ..." instead of "btrfs filesystem scrub ..." - ability to scrub a single device instead of a whole file system - superfluous command line options removed - resume is now a separate command ("scrub resume") instead of "scrub start -r" -

Hi folks! Been using btrfs for quite a while now, worked great until now. Got power-loss on my machine and now i have the "parent transid verify failed on X wanted X found X" problem. So I can''t get it to mount. My btrfs is spread over sda (2tb), sdc(2tb), sdd(1tb). Is this something that an offline fsck could fix ? If so is the fsck-util being developed ? Is there a way to

...t and the second host and the third, or if it is because my first host is defined by IP, and the second two are define by hostname. But the cause is likely one or the other. hostnames and ips are omitted, but you should get the idea. *%cat /etc/exports * /gpfs/nfs/share n.n.n.n(rw,root_squash,fsid=nnn) n.n.n.n(rw,root_squash,fsid=nnn) n.n.n.n(rw,root_squash,fsid=nnn) *%showmount -e nnnn* Export list for nnnn: /gpfs/nfs/share n.n.n.n *%exportfs -r* *%showmount -e nnnn* Export list for nnnn: /gpfs/nfs/share n.n.n.n, n.n.n.n, n.n.n.n regards, Charles

...pper/vg00-btrfsvol0_0 /mnt/btrfs0 mount: wrong fs type, bad option, bad superblock on /dev/mapper/vg00-btrfsvol0_0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so I checked dmesg: [17216.145092] device fsid c959d4a5-0713-4685-b572-8a679ec37e20 devid 1 transid 34 /dev/mapper/vg00-btrfsvol0_0 [17216.145639] btrfs: disk space caching is enabled [17216.146987] btrfs: failed to read the system array on dm-100 [17216.147556] btrfs: open_ctree failed Then I did btrfsck - it reported no errors, but mounted...

...rver on Linux Arch (kernel 3.11.2) that uses multi-device btrfs on root filesystem. Until recently it worked completely fine. And yesterday I rebooted it and the machine did not wake up. I booted from a USB (kernel 3.10) and tried to mount the filesystem. Here is OOPs I see [ 41.676217] device fsid 25e6a6fa-fe1f-4be5-a638-eeac948f8c21 devid 8 transid 164237 /dev/sda [ 41.684161] btrfs: disk space caching is enabled [ 67.266742] BTRFS error (device sdd3): block group 1141416919040 has wrong amount of free space [ 67.266796] BTRFS error (device sdd3): failed to load free space cache for b...

we recently deployed some large XFS file systems with centos 6.2 used as NFS servers... I've had some reports of a problem similar to the one reported here... http://www.linuxquestions.org/questions/red-hat-31/xfs-inode64-nfs-export-no_subtree_check-and-stale-nfs-file-handle-message-855844/ these reports are somewhat vague (third indirectly reported via internal corporate channels from

...---------------------------- "show" doesn''t show any part of the bundle of 3 partitions. That''s more than I''ve expected from the option "delete" ... ------------------------------------------------- Famous last words from "dmesg": device fsid 6bd7d4df-e133-47d1-9b19-3c7565428770 devid 3 transid 437 /dev/sdm1 device fsid 6bd7d4df-e133-47d1-9b19-3c7565428770 devid 2 transid 437 /dev/sdl1 device fsid 6bd7d4df-e133-47d1-9b19-3c7565428770 devid 4 transid 437 /dev/sdj1 device label SCSI devid 1 transid 7 /dev/sdj1 btrfs: disk space caching is...

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 doesn''t work...