| 1 |
On Monday 30 November 2009 05:54:31 Mike Diehl wrote: |
| 2 |
> Hi all, |
| 3 |
> |
| 4 |
> I recently moved my local home directory to an nfs-mounted directory. Now |
| 5 |
> I'm having trouble with kmail. It seems that the permissions on |
| 6 |
> ~/.kde/share/apps/kmail/mail/sent-mail/cur are being... changed... |
| 7 |
> |
| 8 |
> What I'm seeing is this: |
| 9 |
> |
| 10 |
> drwxrwxrwx 5 mdiehl users 4096 2009-11-28 03:41 . |
| 11 |
> drwx------ 8 mdiehl mdiehl 4096 2009-11-29 18:43 .. |
| 12 |
> d????????? ? ? ? ? ? cur |
| 13 |
> drwx------ 2 mdiehl users 4096 2009-09-02 19:32 new |
| 14 |
> drwx------ 2 mdiehl users 4096 2009-11-29 18:43 tmp |
| 15 |
|
| 16 |
That is indicative of filesystem corruption where the kernel cannot read the |
| 17 |
directory for whatever reason. The server should always be able to read the |
| 18 |
inode for cur/ and read the owner/permissions data |
| 19 |
|
| 20 |
What nfs options are in use, both client and server side? |
| 21 |
|
| 22 |
> Then, after a while, the permissions get changed to something more sane |
| 23 |
> without me having done anything. |
| 24 |
|
| 25 |
Permissions don't just magically change. Either a cron runs that changes |
| 26 |
things, or a circumstance changes to allow the client to see the directory |
| 27 |
|
| 28 |
> I've googled for this and not found anything. Strangely, kmail won't start |
| 29 |
> unless it can read my sent-mail folder. |
| 30 |
|
| 31 |
That's not strange at all, an MUA that can't use it's sent folder is pretty |
| 32 |
useless as an MUA |
| 33 |
|
| 34 |
-- |
| 35 |
alan dot mckinnon at gmail dot com |
Archives