https://bugzilla.novell.com/show_bug.cgi?id=714151 https://bugzilla.novell.com/show_bug.cgi?id=714151#c zj jia changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@suse.com AssignedTo|bnc-team-screening@forge.pr |nfbrown@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=714151 https://bugzilla.novell.com/show_bug.cgi?id=714151#c2 --- Comment #2 from Diego Ercolani 2011-09-07 13:46:09 UTC --- (In reply to comment #1) I confirm that with fsid=0 It seems to work.

From the exports manual page:

fsid=num|root|uuid NFS needs to be able to identify each filesystem that it exports. Normally it will use a UUID for the filesystem (if the filesystem has such a thing) or the device number of the device holding the filesystem (if the filesystem is stored on the device). As not all filesystems are stored on devices, and not all filesystems have UUIDs, it is sometimes necessary to explicitly tell NFS how to identify a filesystem. This is done with the fsid= option. For NFSv4, there is a distinguished filesystem which is the root of all exported filesystem. This is specified with fsid=root or fsid=0 both of which mean exactly the same thing. Other filesystems can be identified with a small integer, or a UUID which should contain 32 hex digits and arbitrary punctu- ation. Linux kernels version 2.6.20 and earlier do not understand the UUID setting so a small integer must be used if an fsid option needs to be set for such kernels. Setting both a small number and a UUID is supported so the same configuration can be made to work on old and new kernels alike. buti it seem that btrfs have its own uuid, in my case: Label: 'usr' uuid: cb9b8f2b-f590-49c1-a896-7f372732a00a Total devices 1 FS bytes used 2.56GB devid 1 size 10.00GB used 5.04GB path /dev/dm-1 Label: 'vecchiopcrootfs' uuid: 7ae3bf35-4c50-40ef-afe5-6e59272e389e Total devices 1 FS bytes used 14.94GB devid 1 size 24.00GB used 21.04GB path /dev/dm-2 Label: 'samba' uuid: 44f76b1a-a414-40f5-a917-0d0a78b47fb0 Total devices 1 FS bytes used 54.05GB devid 1 size 100.00GB used 70.29GB path /dev/dm-3 Label: 'virtualmachines' uuid: d5d0ac81-3754-40ef-86b4-7b1fa6fb7b02 Total devices 1 FS bytes used 94.74GB devid 1 size 150.00GB used 98.29GB path /dev/dm-7 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=714151 https://bugzilla.novell.com/show_bug.cgi?id=714151#c4 Diego Ercolani changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|diego.ercolani@gmail.com | --- Comment #4 from Diego Ercolani 2011-09-08 08:05:47 UTC --- Created an attachment (id=449717) --> (http://bugzilla.novell.com/attachment.cgi?id=449717) trace as requested (showmount -e localhost; exportfs ...; showmount ...; mount ..; (In reply to comment #3) Neil, as I have problem exporting btrfs, I don't export different partitions with the same fsid, I don't currently export at all. (The original partition /dev/mapper/nonraid-ISO it's currently an ext4 filesystem) I only tried with your suggestion to give a try. But, if you want the strace file I'm going to provide you. (for information the partition I'm trying to export (without fsid) it's my /usr directory pc-diego:~ # rcnfsserver status Checking for kernel based NFS server: idmapd running mountd running statd running nfsd running pc-diego:~ # ps axuww | grep mountd root 8433 0.0 0.0 19760 1128 ? Ss 09:57 0:00 /usr/sbin/rpc.mountd root 8477 0.0 0.0 6780 856 pts/1 S+ 09:57 0:00 grep mountd pc-diego:~ # showmount -e localhost Export list for localhost: /dati/ISO * pc-diego:~ # exportfs -o ro,no_root_squash *:/usr pc-diego:~ # showmount -e localhost Export list for localhost: /usr * /dati/ISO * pc-diego:~ # mount 127.0.0.1:/usr /mnt/tmp/ mount.nfs: Connection timed out pc-diego:~ # -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=714151 https://bugzilla.novell.com/show_bug.cgi?id=714151#c6 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nfbrown@suse.com AssignedTo|nfbrown@suse.com |puzel@suse.com --- Comment #6 from Neil Brown 2011-09-08 21:34:34 UTC --- Yes, definitely a bug in util-linux. In sysfs_init in particular (in lib/sysfs.c) If the 'open' fails we 'goto err' which runs 'sysfs_deinit()' on a 'cxt' which hasn't been fully initialised. The 'dir_fd' is still 0, so sysfs_deinit calls "close(0)" is confused things. Fix is o set dir_fd to -1 immediately after the memset in sysfs_init. I'll this over the Petr - util-linux maintainer. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=714151 https://bugzilla.novell.com/show_bug.cgi?id=714151#c Petr Uzel changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Status Whiteboard| |util-linux -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=714151 https://bugzilla.novell.com/show_bug.cgi?id=714151#c9 --- Comment #9 from Bernhard Wiedemann 2011-09-13 12:00:22 CEST --- This is an autogenerated message for OBS integration: This bug (714151) was mentioned in https://build.opensuse.org/request/show/81983 Factory / util-linux -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.