Re: Ext3 filesystem errors - orphaned inodes - continued

2010-11-27 Thread Cyanrigger
sf...@users.sourceforge.net wrote: My English and brain are broken, sorry. Hehehe ;) I am also not a native english speaker. But I think we'll work it out. Nevertheless, you are a wizard :D Here is my guess. - syslogd opens these log files for write. - in the beginning, files exist on

Re: Ext3 filesystem errors - orphaned inodes - continued

2010-11-27 Thread sfjro
Cyanrigger: rsync copies the file. the target file is removed but ext3 doesn't release the resources for the file since the inode is still referenced and alive. Wow. That really bends my brain. You say that the target file is removed at copying. So this is the reason why the inode of the

Re: Ext3 filesystem errors - orphaned inodes - continued

2010-11-27 Thread Cyanrigger
sf...@users.sourceforge.net wrote: If I do the same on a pure ext3 system, the inode number of the file is not being changed if I copy new content in it. It is just the case if I do some kind of copy-on-write. I might misunderstand the behaviour of rsync. I thought it operats - create

Re: Ext3 filesystem errors - orphaned inodes - continued

2010-11-27 Thread sfjro
Cyanrigger: No, I made a mistake and made the test with just a cp, which behaves like I said and I assumed rsync would do the same. Now I also know what these --delete-X parameters of rsync do. AFAIK you're right about the behaviour of rsync and your explanation in your second-last post

Re: Ext3 filesystem errors - orphaned inodes - continued

2010-11-27 Thread sfjro
sf...@users.sourceforge.net: Do you consider this a bug in aufs, though? No. I think it is a problem of your shutdown script. Generally any shutdown script executes - kill all processes - remount / readonly For the system whose root is aufs, the similar scirpt but more work is

Re: Ext3 filesystem errors - orphaned inodes - continued

2010-11-27 Thread Michael S. Zick
On Sat November 27 2010, sf...@users.sourceforge.net wrote: sf...@users.sourceforge.net: Do you consider this a bug in aufs, though? No. I think it is a problem of your shutdown script. Generally any shutdown script executes - kill all processes - remount / readonly For the

Re: Ext3 filesystem errors - orphaned inodes - continued

2010-11-27 Thread Cyanrigger
Hi, sf...@users.sourceforge.net: Do you consider this a bug in aufs, though? No. I think it is a problem of your shutdown script. Generally any shutdown script executes - kill all processes - remount / readonly For the system whose root is aufs, the similar scirpt

Re: Ext3 filesystem errors - orphaned inodes - continued

2010-11-27 Thread sfjro
Cyanrigger: I think it is a problem of your shutdown script. Generally any shutdown script executes - kill all processes - remount / readonly For the system whose root is aufs, the similar scirpt but more work is necessary. In your case, - remount ext3 readwrite