Salix OS

Hi,

I just threw a CD containing CDA tracks into the CD-ROM drive. The system was then trying to start the video
and was frozen soon afterwards.
Only a reset could help...

Is this a "normal" behaviour, or where to look to find the cause?

Does this CD contain a video? CD-Extra or something?

Probably not...

I had the same thing happened to me some times back with a regular audio CD.

Hi,

no, as far as I can see, there are no extras on that CD.
At least not obvious and invisible, if any...
Just cda tracks....

To try to have some clues, uncheck the "play CD audio when inserted" in thunar-volman prefs, put a CD audio in your drive, open a terminal, run totem and listen to your CD.
If something goes wrong and with luck you will have some logs on your terminal.

++

ok,

I would like to explore this a bit!

Last time when I had to reset the machine, claws lost a folder connection...no real data just the link to one of my mailboxes! So I want to do it safe!
Does XFS autocheck the file system for errors or do I need to kick kind of "chkdsk" off manually or via script or the like?
What is the safest way to do what is proposed?
Where/how to uncheck the "autoplay" option for CD-ROM drives?
Could I redirect the log (if any) directly into a text file? How2do?

Thanks for helping me getting on the road!

You can disable the autoplay by running the Thunar Volume manager. It's somewhere in the menu as "Removable Drives and Media" or from the command line with /usr/libexec/thunar-volman-settings

jpg153 wrote:Does XFS autocheck the file system for errors or do I need to kick kind of "chkdsk" off manually or via script or the like?

Yes, all file systems are automatically checked if they weren't cleanly unmounted before. But remember: These checks only bring the file system to a clean state again, but they can NOT recover all your data if power fail/reset is done during a writing operation. Of course some file systems can handle this better than others, but generally said you just need a bit luck

Sure,
but XFS as a journaling file system should be able to recover most data. To get all back is about luck - you are right!

jpg153 wrote:a journaling file system should be able to recover most data

That's a widely spread misbelief In simple words the journal only contains informations about WHERE data on the disk is changed but not WHAT data is changed. As I've said these informations are used to get the file system in a consistent state again without running ever lasting fsck checks.

PS: AFAIK some journaling file systems can be tweaked to even store what is written on the disk, but this results in a 50 % performance impact because all data is written twice.