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
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
On Mon, 26 Nov 2001, Kenneth D. Merry wrote:
So did you try the statically linked -stable binary on -current?
Yes, I used the newest version from the ports (compiled on -CURRENT) and
the staticly linked from -STABLE both on -CURRENT, and the CDs are
identical.
Is it completely static?
On Mon, 26 Nov 2001, Joerg Wunsch wrote:
Kenneth D. Merry [EMAIL PROTECTED] wrote:
Are there any areas with good data on the CD? i.e. can you see any
pattern to the corruption? If you compare the same CD burned from
-current and -stable you might begin to see a patern.
I tried a
As Christoph Herrmann wrote:
Maybe there are other problems. But I had no problems (burning CDs
on -CURRENT) until the beginning of october. (I run make world about
once a week). And with -STABLE everything is fine until now. It is
the same box, I (try to) burn the same image, the only
On Mon, Nov 26, 2001 at 16:26:18 +0100, Christoph Herrmann wrote:
Hi,
Im running -STABLE and -CURRENT from different disks on the same box.
And with -STABLE there are no problems burning CDs with a YAMAHA CRW6416S
on an Adaptec 2940.
But withs -CURRENT all CDs are broken. Cdrecord produces
Kenneth D. Merry [EMAIL PROTECTED] wrote:
Are there any areas with good data on the CD? i.e. can you see any
pattern to the corruption? If you compare the same CD burned from
-current and -stable you might begin to see a patern.
I tried a test-burn with a FreeBSD-current from yesterday, on
