On 12/13/2001 09:28 PM, Dieter Nützel wrote: > Am Donnerstag, 13. Dezember 2001 20:44 schrieb Manuel Krause: > >>On 12/13/2001 07:53 PM, Dieter Nützel wrote: >> >>>Am Donnerstag, 13. Dezember 2001 10:26 schrieben Sie: >>> >>>>Dieter Nützel wrote: >>>> >>>>>On Thursday, 13. December 2001 03:15 you wrote: >>>>> >>[...] >> > > [-] > >>I compiled Dieters patch combination this morning except for bootmem and >>nanosleep. >> > > They shouldn't harm. Even Preempt + lock-break (including the latest ReiserFS > lock-break ;-)
You mean lock-break-rml-2.4.17-pre8-1.patch or something very special? ;-) > > >>After some minutes uptime I got disappearing files with this >>behaviour >> rm: cannot remove `/dev/parport16': No such file or directory >> mknod: `/dev/parport16': File exists >> >>and many lines vs-15011: reiserfs_release_objectid: tried to free free >>object id (.....) >> > > Yes, had such messages, too. > > >>Of course, I was not able to set (or get) permissions for those files... >> >>reiserfsck --check said --fix-fixable would solve the problems but it >>didn't catch all. For now, I can say --rebuild-tree completely recovered >>the filesystem. (reiserfsprogs 3.x.0k-pre13) >> > > Have you rebooted after that? > I had your feeling, too but after reboot. --- Bang all problems were there, > again... First I rebooted after --rebuild-tree to the same kernel and some minutes later the problems came up again. Yes. I repeated --rebuild-tree and booted to my old kernel (2.4.16 + reiserfs A..N + Andrew Mortons low-latency patch). Everything was restored o.k. then. Until... > >>This patch combination didn't seem to affect my ext2 partition at all. >>As I never had the inode-attrs patch running but patches A..P >> > > You mean 2.4.16 + A-P except O and 2.4.17-pre4 and above + K-P except O, > right? Had you applied Chris's expanding-truncate-4.diff. > ...I then combined 2.4.16 + A..N + P + Chris's expanding-truncate-4.diff + low-latency. I got these disappearing files again afterwards. So again --rebuild-tree and so on. Now I have 2.4.17-pre8, K..N+P + preempt-1 + lock-break-1 running. (I didn't try 2.4.17-pre4) Except for these many vs-15011 lines I didn't see a problem so far. > >>work well >>with 2.4.16 there's something incompatible within the others. >> >>Maybe someone wanted this additional information. >> > > Thanks, so didn't have to go back, only drop O...;-) > It's very clear now that the expanding-truncate-4 patch needs to be excluded and/or adjusted, too. :-) I hope that works for you after your inode-attrs experiment! Manuel
