This is not a problem with sshfs or squashfuse. How on earth do I recover from this? Pardon me if this sounds abrasive, it isn't meant to, but isn't the main point of FUSE to avoid stuff like this? That is, keep away from kernel-space so you cannot cause lockups like this?ĭo I really have to reboot? Because I'm halfway through a 4-terabyte file operation that I would then have to start all over, losing about 20 hours of computational work :/ That's okay for now, but if this is expected behavior going forward, that's pretty depressing news, because I have big plans for squashfs and unionfs on this rig :D They just go into zombie mode, and everything still hangs. I've tried killing processes that relate to fuse or mount, but to no avail. ls, umount, sudo umount -f, diskutil unmount force, you name it. Using bash, I can type things - and commands - but anything that "touches" the mountpoint hangs irrevocably. The instant I start zsh, it hangs (I assume due to oh-my-zsh doing some autocomplete stuff as soon as I start pressing keys). Which resulted in fuse: unknown option 'dmesk=0000'. Squashfuse -o dmesk=0000,fmask=0111 pictures.squashfs mnt Muddled around on the interwebs, then tried mounting with this typo: I then wanted to find out how to make everything r/w (I'll be using UnionFS on top of squashfs, and I want everything to be writable to everyone). I was playing around with squashfs-fuse, and created a test squashfs, pictures.squashfs, then mounted it successfully under ~/mnt, and had a look around.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |