![]() ![]() I'm marking this as solved, but I'd like to hear how to handle this in the future - I don't want to mess up ZFS every time it fails to start. I've disabled zfs.target service, rebooted, noted that everything under /storage is empty, did a "mv /storage /storage.bak", and started zfs.target without issues! After I had ZFS working I could reenable all services. cannot mount /export/home/lalt: directory is not empty use legacy mountpoint to. Here's what happened - after kernel upgrade, ZFS couldn't start, but the Docker container I've mentioned (not just that, I also had some other stuff symlinked to some datasets) started and created stuff on /storage/.whatever Any dataset whose mountpoint property is not legacy is managed by ZFS. So my customer made a partition of type vmware vmfs and. In 'df -h' it shows as a 'VMWARE VMFS' system, it should show 'Linux'. The partition type is not the same as the filesystem on it. According to him and his testing done in his lab it has to do with the formatting of the disk. I also removed all symlinks to /storage/* I had in my home directory since I remember that I had some troubles with managing datasets which had symlinks, not sure what it was. Alternately, if you pass the zfsutil option to mount and make it think the caller was zfs (8) it should work too, mount -o remount,ro,zfsutil /. Past friday I received a solution from the symantec engineer. ![]() "tree *" on /storage gives 0 directories and 0 files, so I'm not sure what is causing the "cannot mount '/storage': directory is not empty" message when I do a "zfs mount -a". I didn't know how to locate which files were also created, so I upgraded the kernel again, rebooted (ZFS fails to start), did a "ls -R" on /storage and it listed all datasets just under /storage (depth 1, so nothing under that first level) - is that how it should be even though ZFS didn't start? I removed traces of that container, but "zfs mount -a" would still complain about /storage. I'm guessing that when ZFS failed to start (after my kernel upgrade), Docker created that path anyway, which in turn prevented ZFS to mount it after I downgraded kernel. I had a Docker container started with -v /storage/services/gitlab, and "zfs mount -a" was complaining about that particular path. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |