![]() 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. 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 ![]() 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. This directory is created as needed, and ZFS automatically mounts the file system. mountpoint property of the ZFS pool pool1 as follows: sudo zfs set mountpoint/mypool pool1. herrchen Beiträge: 3257 Registriert: 18:45:28 Lizenz eigener Beiträge: MIT Lizenz Wohnort: Berlin. "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". A file system can also have a mount point set in the mountpoint property. Directory /mnt/ssd is empty and is not a Proxmox storage. fusermount: mountpoint is not empty fusermount: if you are sure this is safe, use the nonempty mount option notebook:/home/sibru Mit Konqueror kann ich auf den FTP-Server und auf das Verzeichnis /music zugreifen. ![]() 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 |