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 oth
On Wed, Nov 28, 2001 at 15:44:37 +0100, 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
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 Tue, Nov 27, 2001 at 09:06:48 +0100, Christoph Herrmann wrote:
> 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
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 di
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.
>
>
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? (i.
"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 yesterd
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 pro
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 no Error messages
and exits normaly, but there are areas with binary zer
11 matches
Mail list logo
