Hello all. I am working on an NFS failover scenario between two servers. I am getting the stale file handle errors on my (linux) client which point to there being a mismatch in the fsid's of my two filesystems when the failover occurs. I understand that the fsid_guid attribute which is then used as the fsid in an NFS share, is created at zfs create time, but I would like to see and modify that value on any particular zfs filesystem after creation.
More details were discussed at http://www.mail-archive.com/zfs- [EMAIL PROTECTED]/msg03662.html but this was talking about the same filesystem sitting on a san failing over between two nodes. On a linux NFS server one can specify in the nfs exports "-o fsid=num" which can be an arbitrary number, which would seem to fix this issue for me, but it seems to be unsupported on Solaris. Any thoughts on workarounds to this issue? Thank you kind sirs and ladies. Asa -hack On Nov 10, 2007, at 10:18 AM, Jonathan Edwards wrote: > Hey Bill: > > what's an object here? or do we have a mapping between "objects" and > block pointers? > > for example a zdb -bb might show: > th37 # zdb -bb rz-7 > > Traversing all blocks to verify nothing leaked ... > > No leaks (block sum matches space maps exactly) > > bp count: 47 > bp logical: 518656 avg: 11035 > bp physical: 64512 avg: 1372 > compression: 8.04 > bp allocated: 249856 avg: 5316 > compression: 2.08 > SPA allocated: 249856 used: 0.00% > > but do we maintain any sort of mapping between the object > instantiation and how many block pointers an "object" or file might > consume on disk? > > --- > .je > > On Nov 9, 2007, at 15:18, Bill Moore wrote: > >> You can just do something like this: >> >> # zfs list tank/home/billm >> NAME USED AVAIL REFER MOUNTPOINT >> tank/home/billm 83.9G 5.56T 74.1G /export/home/billm >> # zdb tank/home/billm >> Dataset tank/home/billm [ZPL], ID 83, cr_txg 541, 74.1G, 111066 >> objects >> >> Let me know if that causes any trouble. >> >> >> --Bill >> >> On Fri, Nov 09, 2007 at 12:14:07PM -0700, Jason J. W. Williams wrote: >>> Hi Guys, >>> >>> Someone asked me how to count the number of inodes/objects in a ZFS >>> filesystem and I wasn't exactly sure. "zdb -dv <filesystem>" seems >>> like a likely candidate but I wanted to find out for sure. As to why >>> you'd want to know this, I don't know their reasoning but I >>> assume it >>> has to do with the maximum number of files a ZFS filesystem can >>> support (2^48 no?). Thank you in advance for your help. >>> >>> Best Regards, >>> Jason >>> _______________________________________________ >>> zfs-discuss mailing list >>> zfs-discuss@opensolaris.org >>> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >> _______________________________________________ >> zfs-discuss mailing list >> zfs-discuss@opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
