Incorrect f.s. info

Zigbert has described this problem here:
http://murga-linux.com/puppy/viewtopic.php?t=32882&start=30

He burns to a CD in multisession mode, then burns another track, but after mounting the CD the 'ls' command shows the old contents. The CD has to be physically ejected then reinserted then mounted to force the system to update the f.s. info.

I think this problem is only with the new libata PATA/SATA drivers, not with the old IDE drivers, so you won't have it on the 4.1retro Puppy.

I have just been sitting here for a few hours, trying all sorts of things to try to force a refresh without having to eject the CD, but no-go. This is a fundamental problem with the kernel and libata, and yet another thing they need to address.

---

Comments

Maybe autoeject
Username: Rarsa
Maybe that's why all burning software I've ever used ejects the CD after burning even if it has to be reinserted for CD verification. That sounds like a posible "woraround".

Cdrom experience
Username: Jesse
"Cdroms break some unix notions, they are not precisely just a block device, and not precisely just a character device. They are both. The usual notion for a data cdrom disk is that it is a block device with a filesystem, burning a cdrom changes the number of blocks (via ioctls / scsi commands), and the kernel block cache doesn't pay attention to those commands to notice the changes. To get the kernel to notice the changes, the burning program must close its filedescriptor, ask the cdrom drive to clear its buffer cache, make sure no other program has the filedescriptor open, clear the kernels block cache for the cdrom drive, wait for the kernel to free its cdrom filedescriptor structures, reopen the filedescriptor, ask the cdrom to be rescanned. And then this may not work with all cdrom drives, but I suppose you could then eject it. Phew! Sometimes its just easier to eject! which does all those things above.

Pburn/Pbackup
Username: Zigbert
"jake_take reported that Pschedule doesn't keep crontab for next boot on his usb installation, because /var/ is not saved. This works in frugal install. Is it supposed to differ, or ... http://www.murga-linux.com/puppy/viewtopic.php?t=22166&start=15

/var not saved
Username: BarryK
"zigbert, yes, that is inconsistent. I'll look into it.

Tags: puppy