Skip to contentSkip to conversation

Error on fs unmount

DISCUSSION Peter Klotz 3 participants 5 messages Aug 17, 2001

lore
Share & tools
lore
#0 lore raw

Hi developers

Kernel 2.4.8 produces the following message on almost every shutdown:

Unmounting filesystems: Trying to _clear_inode of system file 9! Shouldn't happen.

This did not occur in 2.4.6 and prior.

Is this an issue?

Please CC to me since I am not on the list.

Bye, Peter.

#1 lore raw
Quoted 4 lines · Peter Klotz

Kernel 2.4.8 produces the following message on almost every shutdown:

Unmounting filesystems: Trying to _clear_inode of system file 9! Shouldn't happen.

Please tell us what filesystem you are using?

Assuming ext2, please run "e2fsck -f <device>" on the unmounted filesystem. However, since I've never seen this message before, and e2fsck would run automatically after such an error I doubt it is ext2 unless there were recent changes.

Cheers, Andreas

Signature · 3 lines
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert
#2 lore raw
Quoted 7 lines · Andreas Dilger
Quoted 4 lines · Peter Klotz

Kernel 2.4.8 produces the following message on almost every shutdown:

Unmounting filesystems: Trying to _clear_inode of system file 9! Shouldn't happen.

Please tell us what filesystem you are using?

He is using NTFS. I recognize my error message. (-; [A little omission of mine results in not getting the string "NTFS: " printed at the beginning of the error message. )-: Fixed in my tree and will be in next patch release.]

Peter,

Could you tell me whether on startup (or whenever you mount the NTFS volume) it doesn't give a message but saying: "Trying to open system file 9!" or "Opening system file 9!".

If you only get the _clear_inode message that would be bad, but if you get a corresponding "Trying to open..." message, then just ignore them for the moment. - This is part of stage one of a cleanup in ntfs system file handling and this is just a message telling you someone is trying to close a system file which hasn't been opened yet, which should indeed never happen. - This will disappear with my next update to ntfs which completes the system file cleanup stuff.

If you only get the _clear_inode message this is very bad and I would like to know more... but I suspect you will find the matching message.

Best regards,

Anton

Signature · 5 lines
  "Nothing succeeds like success." - Alexandre Dumas
-- 
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS Maintainer / WWW: http://linux-ntfs.sf.net/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/
#3 lore raw
In reply to Peter Klotz
Quoted 5 lines

Peter,

Could you tell me whether on startup (or whenever you mount the NTFS volume) it doesn't give a message but saying: "Trying to open system file 9!" or "Opening system file 9!".

You were right. I found the message you mentioned several times in /var/log/messages:

Aug 17 08:16:50 localhost kernel: Trying to open system file 9!   

Thanks a lot for your quick and helpful response.

Bye, Peter.

#4 lore raw
Quoted 7 lines · Peter Klotz
Quoted 3 lines

Could you tell me whether on startup (or whenever you mount the NTFS volume) it doesn't give a message but saying: "Trying to open system file 9!" or "Opening system file 9!".

You were right. I found the message you mentioned several times in /var/log/messages:

Aug 17 08:16:50 localhost kernel: Trying to open system file 9!

Excellent. That is exactly what I expected to see, so all is fine. Just ignore for now.

Quoted 1 line

Thanks a lot for your quick and helpful response.

You are welcome.

Cheers,

Anton

Signature · 5 lines
  "Nothing succeeds like success." - Alexandre Dumas
-- 
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS Maintainer / WWW: http://linux-ntfs.sf.net/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/