2

We have an older file server (running Gentoo of all things) that recently suffered a storage controller failure. The parts were replaced and everything is back online except one item, probably the most important: the ESXi mount point.

The former sysadmin, while brilliant, never kept notes for any changes. There's nothing in FSTAB or CRONTAB or any 'normal' place to create mounts. Running zfs list shows all the ZFS mount names, but has a blank for the mount point. My coworker and I are poring through log files trying to find any indication of historical mounts, but there's nothing. This is connected to the open-source licensed compute server via infiniband, but unsure whether it's shared via NFS, iSCSI, or what. Like I said, no notes to work from.

Improve this question
4
  • 1
    Anything in /etc/exports?
    – jordanm
    Jan 3, 2017 at 18:05
  • 1
    Nothing, however, I was reading another thread that I checked before I posted this and ran a hexdump -C </dev/ | head -40 on two partitions that showed up as unformatted during a fdisk -l. The curious thing is that part of the output shows this in the right margin: naa.6001405caf12eb39b604499954050669:1 looks like ESXi volume to me, but I'm unfamiliar with the hexdump command.
    – Christian Holton
    Jan 3, 2017 at 18:14
  • zfs get mountpoint all ?
    – ewwhite
    Jan 3, 2017 at 18:20
  • 1
    @ewwhite that lists all the mountpoints, but is missing a value for our share. For example, there is a share for our Xenserver called xenserver-vhd, and it's got a corresponding mountpoint called the same. The value for esxivhd, but the value is merely -.
    – Christian Holton
    Jan 3, 2017 at 18:24

1 Answer 1

Reset to default
1

This is so little information to go on, but I'll try to edit this answer as needed...

Please show the output of:

zpool list zpool status -v zfs list

And possibly http://pastebin.com the zpool history output for me.

Okay, that fileserver is a terrible mess. I'm sorry your organization is in this situation without documentation.

I'm actually concerned about how this was done... It's a perfect example of unpaid technical debt... but the core issue is that your Xen and VMware shares are not NFS. They are comprised of ZFS zvols here. That means that ZFS is presenting a block device to the hypervisors that's formatted using their native filesystems. I don't know if iSCSI is in the mix here, but if you post zpool history, I may be able to determine what was done.

Improve this answer
9
  • 1
    pastebin.com/zvD4SsdR
    – Christian Holton
    Jan 3, 2017 at 18:29
  • There's only one mention of /tank/esxvhd that that's it's creation in 2015. pastebin.com/7jDhvNke
    – Christian Holton
    Jan 3, 2017 at 18:40
  • That's correct. It's a non-sparse ZFS zvol. Please post zfs get all tank/esxvhd
    – ewwhite
    Jan 3, 2017 at 18:42
  • cannot open 'tank/esxvhd': dataset does not exist
    – Christian Holton
    Jan 3, 2017 at 18:45
  • 3
    @ChristianHolton This is beyond the level of help I can provide for free online. This is definitely solvable, but is something I'd set up a normal support engagement for. My contact information is in my ServerFault profile page. Your previous engineer left a bit of a mess and constructed a fragile solution. You may want to contact them to see if there's a quick fix.
    – ewwhite
    Jan 3, 2017 at 20:14

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .