Re: Not all files are deleted
Hello, > Philippe Malinge: > > please find attached strace files for each round of "rm -fr dummy.3312" > > executed on nfs-client side. > > strace files are named using the round number (1, 2, 3, 4, 5) > > Thank you for your test. > I believe it is a known problem which was reported recently by a few > people. I could reproduce your problem. If your 'rm' command version is less than 'rm (GNU coreutils) 6.9+', please try the latest 'rm.' I will try aufs will work on older rm, but it may be hard. Junjiro Okajima - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
Re: "au_new_inode: broken ino"
> "Jrgen P. Tjern": > > [2297447.631266] aufs 20070702 > > [2297509.899071] aufs au_new_inode:347:smbd[27416]: Un-notified UDBA or > > directly renamed dir, b0, xfs, Simon - Garfunkel - The Best Of Simon - > > Garfunkel - Song For The Asking.mp3, hi1610612893, i16. Please show me your /sys/fs/aufs/*/xino file, if it exists. And please try this patch. Junjiro Okajima -- Index: fs/aufs/xino.c === RCS file: /cvsroot/aufs/aufs/fs/aufs/xino.c,v retrieving revision 1.32 diff -u -p -r1.32 xino.c --- fs/aufs/xino.c 2 Jul 2007 05:11:13 - 1.32 +++ fs/aufs/xino.c 2 Jul 2007 12:58:23 - @@ -151,7 +151,8 @@ int xino_write(struct super_block *sb, a br = stobr(sb, bindex); AuDebugOn(!br || !br->br_xino); - pos = h_ino * sizeof(*xino); + pos = h_ino; + pos *= sizeof(*xino); sz = xino_fwrite(stosi(sb)->si_xwrite, br->br_xino, xino, sizeof(*xino), &pos); //if (LktrCond) sz = 1; @@ -358,7 +359,8 @@ int xino_read(struct super_block *sb, au br = stobr(sb, bindex); file = br->br_xino; AuDebugOn(!file); - pos = h_ino * sizeof(*xino); + pos = h_ino; + pos *= sizeof(*xino); if (i_size_read(file->f_dentry->d_inode) < pos + sizeof(*xino)) return 0; /* no ino */ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
Re: "au_new_inode: broken ino"
"Jrgen P. Tjern": > [2297447.631266] aufs 20070702 > [2297509.899071] aufs au_new_inode:347:smbd[27416]: Un-notified UDBA or > directly renamed dir, b0, xfs, Simon - Garfunkel - The Best Of Simon - > Garfunkel - Song For The Asking.mp3, hi1610612893, i16. > > It's not an access directly to the underlying fs, so how come this > happens? Is this anything like hte broken_ino? It is equivalent to the old msg 'broken ino.' And as I wrote, it is harmless basically. I think I found the root cause. Probably current aufs cannot handle 'too large inode number', in your case 1610612893 on xfs. The aufs xino file is indexed by the inode number on branch fs. If the inode number is too large, it may exceed the file size limit. Junjiro Okajima - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
Re: "au_new_inode: broken ino"
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: > Hello Jorgen, > > "Jrgen_P._Tjern": >> [EMAIL PROTECTED] wrote: >>> Thank you very much for your tests. >>> Currently I am considering about the bug in aufs inotify handler. >>> Do you know whether this file 'Simon and Garfunkel ... .mp3' has ever >>> been renamed or not? >> (bah, sorry for misposting this reply directly to you, Junjiro) >> >> It shouldn't have been renamed ever, no. :-) > > I think the root cause of this problem is mis-managing inode number > after unlink/rename. > I have re-implemented inode management in aufs, please try the latetest > code. And if the problem (the warning) arise again, please let me know. > > Thank you > Junjiro Okajima I just upgraded to the newest version, and this is my dmesg, shortly after mounting my stuff: [2297447.631266] aufs 20070702 [2297509.899071] aufs au_new_inode:347:smbd[27416]: Un-notified UDBA or directly renamed dir, b0, xfs, Simon - Garfunkel - The Best Of Simon - Garfunkel - Song For The Asking.mp3, hi1610612893, i16. It's not an access directly to the underlying fs, so how come this happens? Is this anything like hte broken_ino? Thanks for your quick responses. :-) Kindest regards, Jørgen P. Tjernø. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGiOWAwqQbW3my7pcRAqaKAJ4zqZKoIyku8aRXxLu5cRq72h/uvgCfbRGm 6NzoaeTneN+5zqAjbAIS84w= =/CGV -END PGP SIGNATURE- - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
Re: "au_new_inode: broken ino"
Hello Jorgen, "Jrgen_P._Tjern": > [EMAIL PROTECTED] wrote: > > Thank you very much for your tests. > > Currently I am considering about the bug in aufs inotify handler. > > Do you know whether this file 'Simon and Garfunkel ... .mp3' has ever > > been renamed or not? > (bah, sorry for misposting this reply directly to you, Junjiro) > > It shouldn't have been renamed ever, no. :-) I think the root cause of this problem is mis-managing inode number after unlink/rename. I have re-implemented inode management in aufs, please try the latetest code. And if the problem (the warning) arise again, please let me know. Thank you Junjiro Okajima - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
