Not sure where to post this…
Situation where RTP mounts an ext2 file system.
If a file is mv then the old and new names both show, it’s not
really “moved” or “renamed” but more like a soft link is created.
If the original filename is then deleted, the link fails, and the
file system is corrupt.
Linux FSCK can repair the error by fixing the dtime on the deleted
inode, but if the system is booted into RTP first, QNX will hang
indefinately recalculating file system stuff for the ext2 file
system on any attempt to mount it, and not fix it.
It appears to be a bug in mv and ext2 compatibility, but the inability
to handle the error in the ext2 file system could be more than a minor
inconvienience.
It’s also true that if the ext2 file system picks up any error for
any reason, or even with no errors, if the flag shows that it was
not properly unmounted, QNX will hang indefinately on any attempt
to access that file system.
Now, I’m not in the “habit” of trashing my file systems, or taking
a system down dirty, so I’m not real enthusiastic about checking to
see if this problem is easily duplicatable
–
Cowboy
‘Mounten’ wird für drei Dinge benutzt: ‘Aufsitzen’ auf Pferde, ‘einklinken’
von Festplatten in Dateisysteme, und, nun, ‘besteigen’ beim Sex.
– Christa Keil
There is a bug in the our ext2 fs shared lib for paritions greater than 2gb
(file corruption). I will see if I can post an update onto developers
corner (developers.qnx.com) under fixes sometime today.
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>
Not sure where to post this…
Situation where RTP mounts an ext2 file system.
If a file is mv then the old and new names both show, it’s not
really “moved” or “renamed” but more like a soft link is created.
If the original filename is then deleted, the link fails, and the
file system is corrupt.
Linux FSCK can repair the error by fixing the dtime on the deleted
inode, but if the system is booted into RTP first, QNX will hang
indefinately recalculating file system stuff for the ext2 file
system on any attempt to mount it, and not fix it.
It appears to be a bug in mv and ext2 compatibility, but the inability
to handle the error in the ext2 file system could be more than a minor
inconvienience.
It’s also true that if the ext2 file system picks up any error for
any reason, or even with no errors, if the flag shows that it was
not properly unmounted, QNX will hang indefinately on any attempt
to access that file system.
Now, I’m not in the “habit” of trashing my file systems, or taking
a system down dirty, so I’m not real enthusiastic about checking to
see if this problem is easily duplicatable >
In this case, the partition is 1417 megabytes.
I post more as point of info in my experience.
It’s not gonna be a problem for me…but thanks
for the fix.
I’ll see if it works next time ( hopefully never )
I run into this
Previously, Adam Mallory wrote in qdn.public.qnxrtp.os:
There is a bug in the our ext2 fs shared lib for paritions greater than 2gb
(file corruption). I will see if I can post an update onto developers
corner (developers.qnx.com) under fixes sometime today.
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net
Not sure where to post this…
Situation where RTP mounts an ext2 file system.
If a file is mv then the old and new names both show, it’s not
really “moved” or “renamed” but more like a soft link is created.
If the original filename is then deleted, the link fails, and the
file system is corrupt.
Linux FSCK can repair the error by fixing the dtime on the deleted
inode, but if the system is booted into RTP first, QNX will hang
indefinately recalculating file system stuff for the ext2 file
system on any attempt to mount it, and not fix it.
It appears to be a bug in mv and ext2 compatibility, but the inability
to handle the error in the ext2 file system could be more than a minor
inconvienience.
It’s also true that if the ext2 file system picks up any error for
any reason, or even with no errors, if the flag shows that it was
not properly unmounted, QNX will hang indefinately on any attempt
to access that file system.
Now, I’m not in the “habit” of trashing my file systems, or taking
a system down dirty, so I’m not real enthusiastic about checking to
see if this problem is easily duplicatable >
–
Cowboy
The IBM purchase of ROLM gives new meaning to the term “twisted pair”.
– Howard Anderson, “Yankee Group”
