Comment 26 for bug 344878
Revision history for this message
| Keith Grizzell (grizzell) wrote Re: file name to long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry) | #26 |
I see these entries in my kern.log but I'm not aware of any particularly long filenames or any files not copying. So, is this *silently* corrupting some collection of files somewhere in the deep recesses of my home directory by not allowing an occasional file to be written? (I.e. I get no warning popup with a siren going off, so should I assume it's being handled gracefully and everything is okay? Or, is the kern.log entry the only warning of an actual problem that the simple end user can expect to get?)
Also, what does it mean when there's a bunch of backslashes instead of a garbled filename in log message?