CD-Rom ,filenames are not displayed correctly

Darklegion · 08-07-2004, 07:55 AM

I seemingly get this after a lazy umount or possibly from mounting multi-session cds,I am not 100% sure.It is really annoying and have not been able to fix it without a reboot.Here is the output I get from 'ls',similar thing under MC and the rest so it is not a bash problem:

Code:

?????????????
??????????????
???????????????????
??????????????????????
?????????????????????????????
??????????????????????????????
???????????????????????????????
???????????????????????????????????
?????????????????????????????????????????????
???????????????????????????????????????????????????????????????
???????????????????????????????????????????????????????????????????
?????????????????????????????????????????????????????????????????????
???????????????????????????????????????????????????????????????????????????????????
??????????????????????????????????????????????????????????????????????????????????????????
???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
????????????????????????????????????????????????????????????????????????

As you can see,just a load of question marks.

Darklegion · 08-12-2004, 10:12 AM

Darklegion · 08-25-2004, 11:23 PM

It happened again and I know it is happening to someone else out there so if you have any info don't hesitate to offer it

.Or at least point me in the right direction such as some handy google terms..I'm not finding any solutions or even people talking of this.And btw it is because of a lazy umount but does not always happen.....seems almost random.And it is unescapable,I.e once it happens nothing short of a reboot has been able to fix it.

Thanks

J.W. · 08-26-2004, 12:12 AM

Have you considered not doing lazy unmounts? If you know that this action is liable to produce this result, perhaps the best solution is to do a regular unmount. -- J.W.

Darklegion · 08-28-2004, 02:46 AM

That is true....however there are times where the cdrom will not unmount even when all processes using it are closed.So a lazy umount works around this and for in most cases it works perfectly.However now and again I get what I posted above and it annoys me

Perhaps it is simply a case of something in particular trying to access the filesystem while I'm lazy umounting,and this corrupts everything.If there were just a way of wiping the slate clean without rebooting i'd be happy.I think I will have another look in to what causes it next time it happens though and I'll have to find a way of checking what processes are accessing what hardware,i'm guessing 'top' or 'ps' can do that for me(I'll take a look at the manuals etc for that )

Thanks