Christoph Herrmann wrote:
The Problem was the use of vfs.ioopt=2 !
As long as vfs.ioopt is 1 or 2 the CDs are broken and with
vfs.ioopt=0 the CDs are o.k.
I didn't see any other problems with the use of vfs.ioopt=2,
especially no Filesystem corruption :-). Are there other known
The Problem was the use of vfs.ioopt=2 !
As long as vfs.ioopt is 1 or 2 the CDs are broken and with
vfs.ioopt=0 the CDs are o.k.
I didn't see any other problems with the use of vfs.ioopt=2,
especially no Filesystem corruption :-). Are there other known
problems withs vfs.ioopt != 0 ?
Ciao
On 28 Nov, Christoph Herrmann wrote:
The Problem was the use of vfs.ioopt=2 !
As long as vfs.ioopt is 1 or 2 the CDs are broken and with
vfs.ioopt=0 the CDs are o.k.
I didn't see any other problems with the use of vfs.ioopt=2,
especially no Filesystem corruption :-). Are there other
