http://bugzilla.novell.com/show_bug.cgi?id=568319
http://bugzilla.novell.com/show_bug.cgi?id=568319#c11
--- Comment #11 from Carlos Robinson
A kernel dump? I'm investigating how I could do that. For one thing, I only have an ADSL internet connection, upload speed is 300 bits per second.
Wow! Not 300 bits/s, but 300 kbit/s. I guess I'm not to be trusted too much when I'm tired O:-) (In reply to comment #10)
Yes kernel dump would be huge and let us not pursue that route now.
If after all it is needed, I could burn it to a dvd and mail it.
If you can provide more info on the files being opened by mld_hash and par2, that could help my understanding a bit.
Video, avi files. Par2 is very cpu intensive, mld_hash not so. Previously (oS 10.3, 11.0, 11.1) I had this problem with simply copying files, any files. Now it is harder to reproduce, but I'll see if it does by simply copying files. That would be easier to track.
Expecially whether they are working on files in the underlying xfs mount or the exncrypted xfs mount. Just output of commands when you hit this deadlock,
The working should be on the encrypted xfs filesystem. They reside on files (of exactly dvd size), loop mounted, on an underlaying xfs filesystem. I will get the output of the commands this weekend, right now the system is busy and I can't risk crashing it at this moment. I can also provide the exact procedure I used to create these filesystems (at the moment, it is in a mail in Spanish).
mount dmsetup table lsof
This weekend, time permitting :-)
Also whether you can continue to read/write to the underlying xfs partition? Say create a new file on underlying xfs/encrypted xfs after the deadlock?
As far as I remember, no, it locks. I can't even umount them, I have to use: umount -l mountpoint & or it locks that xterm or console.
Thanks for taking the effort to report this issue and providing good amount of info.
And thank you for trying to solve it, I appreciate it. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.