Jeremy Allison schreef op 01-07-2016 19:53:>> So the transition from regular filespace to LUKS filespaces >> (different volume) is not getting this LUKS filespace to appear >> empty to Samba, but not to the linux system itself. Is this to be >> expected? >> >> Is that normal operation, this? > > Hard to tell without logs I'm afraid. We'd need much more data > to tell, but the honest answer is probably "don't do that" :-).I have no other smbd logs other than output that says that some parameter (wide symlinks) is unknown. There is nothing else in there. The previous error (with Truecrypt) was found in some logs though. Basically umount is trying to kill the process, but it is unkillable: Apr 30 00:35:50 diskstation umount: Kill the process "/usr/syno/sbin/smbd" with /store/home/xen. Apr 30 00:35:50 diskstation umount: Kill the process "/usr/syno/sbin/smbd" with /store/home/xen. Apr 30 00:35:50 diskstation umount: Kill the process "/usr/syno/sbin/smbd" with /store/home/xen. Apr 30 00:35:50 diskstation umount: Kill the process "/usr/syno/sbin/smbd" with /store/home/xen. Apr 30 00:35:50 diskstation umount: Kill the process "/usr/syno/sbin/smbd" with /store/home/xen. Apr 30 00:35:50 diskstation umount: Kill the process "/usr/syno/sbin/smbd" with /store/home/xen. Apr 30 00:35:50 diskstation umount: Kill the process "/usr/syno/sbin/smbd" with /store/home/xen. Apr 30 00:35:50 diskstation umount: Kill the process "/usr/syno/sbin/smbd" with /store/home/xen. The unkillable machine ;-). Anyway, this makes it troublesome because I want only a small area of my share to be encrypted ;-). The thing is both data storage (personal files) and a workspace (for when I log into the machine). So basically I need "two" homedirectories..... This is annoying and compicates matters. I have found a solution but now my system hangs. The most annoying thing about samba (and applies to NFS as well) as a client, is that when there is some network error; the entire system may hang as all reads of the root filesystem (or the / directory) can block until that network mount thing is resolved, practically rendering your entire system frozen. Is there not a solution for that?
Am 02.07.2016 um 17:01 schrieb Xen:> The most annoying thing about samba (and applies to NFS as well) as a > client, is that when there is some network error; the entire system may > hang as all reads of the root filesystem (or the / directory) can block > until that network mount thing is resolved, practically rendering your > entire system frozen. > > Is there not a solution for that?that's hardly something which can be changed in the application layer and you have similar problems when write large data to a slow block-device connected with USB -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20160702/694db181/signature.sig>
Xen schreef op 02-07-2016 17:01:> The most annoying thing about samba (and applies to NFS as well) as a > client, is that when there is some network error; the entire system > may hang as all reads of the root filesystem (or the / directory) can > block until that network mount thing is resolved, practically > rendering your entire system frozen. > > Is there not a solution for that?I've had to hard-reset my machine. It is like git reset --hard but not very functional. Sometimes mount will cause a freeze of the / directory with remote (network) filesystems. And sometimes you can only recover by hard-resetting the machine. And then upon reboot, you try the same thing, and no issue at all. (Thank you Harald) I mean, maybe it has nothing to do with NFS or SMBD, but.... I run into this regularly and as such, have regular (perhaps not as often, depends on how much you need to do it) complete system freezes. Reindl Harald schreef op 02-07-2016 17:07:> that's hardly something which can be changed in the application layer > and you have similar problems when write large data to a slow > block-device connected with USBSo do you have any info on whether someone else could fix it? I mean, there must be kernel people that know about it right. Is there a way to file the issue with some bug tracker or something? Somewhere people will notice? The CIFS mount hangs for some reason and the entire system goes down with it. And every process that needs to read the / directory, hangs. And that's your Linux stability, then :S. This can also happen on a server that has an NFS mount. I suppose the reading of / fails because the stat on the mountpoint fails (blocks). So it's probably not only going to be a hanging mount(), but also a subsequent hanging stat(). Serious issue for me.
Am 02.07.2016 um 17:24 schrieb Xen:> Reindl Harald schreef op 02-07-2016 17:07: >> that's hardly something which can be changed in the application layer >> and you have similar problems when write large data to a slow >> block-device connected with USB > > So do you have any info on whether someone else could fix it? I mean, > there must be kernel people that know about it right. Is there a way to > file the issue with some bug tracker or something? Somewhere people will > notice?kernel people are surely aware but it's not all that easy to fix as it appears to be - example: https://lwn.net/Articles/572911/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20160702/9ee659c1/signature.sig>