Re: [Problem] slow write to dvd-ram since 2.6.7-bk8

2005-02-18 Thread Droebbel
On Fr, 2005-02-18 at 00:10 +0100, Tino Keitel wrote:
>On Wed, Feb 16, 2005 at 23:29:24 +0100, Droebbel wrote:
>> On Mi, 2005-02-16 at 22:55 +0100, Droebbel wrote:
>> 
>> >The vmscan-dont-reclaim-too-many-pages.patch led to the said reduction
>> >of writing speed. I reverse-applied it to 2.6.8.1, where it seems to
>> >solve the problem.
>> 
>> Sorry, have to correct that: it seemed to help at my tests with dd
>> (write 1G of zeroes to a file). Copying a file with mc still shows
>> around 1.4MB/s. Could be worse, but is definitely not ok. It *is* better
>> with 2.6.7.
>
>Here are some numbers with my setup. I always wrote 1 GB of data to the
>same DVD-RAM disc (EMTEC), to the device directly and to a fresh ext2
>on
>the disc.
>
>kernel 2.6.10:
>
>$ time { sudo dd if=/dev/zero of=bigfile bs=64k count=16000 ; sync ; }
>
>real32m5.025s
>
>$ time {sudo dd if=/dev/zero of=/dev/cdrom bs=64k count=16000 ; sync ;}
>
>real29m41.980s
>
>kernel 2.6.7:
>
>$ time { sudo dd if=/dev/zero of=bigfile bs=64k count=16000 ; sync ; }
>
>real13m23.688s
>
>$ time {sudo dd if=/dev/zero of=/dev/cdrom bs=64k count=16000 ; sync ;}
>
>real13m14.609s

This is what I get:
 2.6.8 to 2.6.10: about 30 min. I think that's clear now. I did not run
any mre test with that.

2.6.7 gives less than 10 minutes.

Reverse-Patched 2.6.8.1 and 2.6.10 about 9-11 min.

But what I think is interesting: Other than with 2.6.7, with my 2.6.10
the result seems to be highly dependent on other io activities. I came
to test that when I saw that writing to dvd-ram slowed down when reading
from a cdrom at the same time. System disk, cdrom and dvd-ram are
connected by buses as independent as possible: hda, hdd and scd0 via
on-chip ide2. hdc is inactive and spun down at the times of testing.

Some results (same command as yours, but writing to file only):

2.6.8.1 with vmscan-dont-reclaim-too-many-pages.patch
and vmscan-scan-sanity.patch reversed:

real9m17.389s
real10m11.271s
(run twice)

2.6.10, both patches reversed:

real10m26.374s

same kernel, some io and high (but niced) system load by reading from
hda and gzipping into /dev/null

real21m46.795s

same kernel, some io and low load by reading from cdrom (raw read with
dd as well) into /dev/null

real22m11.639s

2.6.7 vanilla, some io and low load by reading from cdrom (raw read with
dd as well) into /dev/null

real5m58.092

That's too fast - impossible on 3x media with verification. I'll check
that again. But it *really* seemed to be fast.

I also hat the impression that my tests with 2.6.10 and 2.6.8.1 were
much more promising when run from a rather basic testing system without
X, a bit closer to the 2.6.7 results. Haven't got time to check that
till monday. All the above results except the 2.6.7 are from Ubuntu
(Hoary) Systems with X and Gnome running. 

Regards
David



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [Problem] slow write to dvd-ram since 2.6.7-bk8

2005-02-17 Thread Tino Keitel
On Wed, Feb 16, 2005 at 23:29:24 +0100, Droebbel wrote:
> On Mi, 2005-02-16 at 22:55 +0100, Droebbel wrote:
> >Some new information:
> >
> >2.6.7 is ok, 2.6.7-mm2 is not ok, 2.6.7 with just the linus-patch from
> >mm2 is ok, 2.6.7 with linus.patch from mm3 isn't.
> >So I took some of the patches from the broken-out mm2 and tested them
> >seperately.
> >
> >The vmscan-dont-reclaim-too-many-pages.patch led to the said reduction
> >of writing speed. I reverse-applied it to 2.6.8.1, where it seems to
> >solve the problem.
> 
> Sorry, have to correct that: it seemed to help at my tests with dd
> (write 1G of zeroes to a file). Copying a file with mc still shows
> around 1.4MB/s. Could be worse, but is definitely not ok. It *is* better
> with 2.6.7.

Here are some numbers with my setup. I always wrote 1 GB of data to the
same DVD-RAM disc (EMTEC), to the device directly and to a fresh ext2
on
the disc.

kernel 2.6.10:

$ time { sudo dd if=/dev/zero of=bigfile bs=64k count=16000 ; sync ; }

real32m5.025s

$ time {sudo dd if=/dev/zero of=/dev/cdrom bs=64k count=16000 ; sync ;}

real29m41.980s

kernel 2.6.7:

$ time { sudo dd if=/dev/zero of=bigfile bs=64k count=16000 ; sync ; }

real13m23.688s

$ time {sudo dd if=/dev/zero of=/dev/cdrom bs=64k count=16000 ; sync ;}

real13m14.609s

Regards,
Tino
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [Problem] slow write to dvd-ram since 2.6.7-bk8

2005-02-16 Thread Droebbel
On Mi, 2005-02-16 at 22:55 +0100, Droebbel wrote:
>Some new information:
>
>2.6.7 is ok, 2.6.7-mm2 is not ok, 2.6.7 with just the linus-patch from
>mm2 is ok, 2.6.7 with linus.patch from mm3 isn't.
>So I took some of the patches from the broken-out mm2 and tested them
>seperately.
>
>The vmscan-dont-reclaim-too-many-pages.patch led to the said reduction
>of writing speed. I reverse-applied it to 2.6.8.1, where it seems to
>solve the problem.

Sorry, have to correct that: it seemed to help at my tests with dd
(write 1G of zeroes to a file). Copying a file with mc still shows
around 1.4MB/s. Could be worse, but is definitely not ok. It *is* better
with 2.6.7.

Regards

David

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [Problem] slow write to dvd-ram since 2.6.7-bk8

2005-02-16 Thread Droebbel
Some new information:

2.6.7 is ok, 2.6.7-mm2 is not ok, 2.6.7 with just the linus-patch from
mm2 is ok, 2.6.7 with linus.patch from mm3 isn't.
So I took some of the patches from the broken-out mm2 and tested them
seperately.

The vmscan-dont-reclaim-too-many-pages.patch led to the said reduction
of writing speed. I reverse-applied it to 2.6.8.1, where it seems to
solve the problem. I also reverse-applied it to the current prepatched
Ubuntu-2.6.10. It helped a bit there. Some new errors since 2.6.8, as it
seems... getting depressing a bit, this whole thing.

If you are using 2.6.7-mm1, there is another patch with even greater
impact: abs-fix.patch. Take the same + abs-fix-fix.patch from mm2.

If you might have a look at the vmscan-dont-reclaim-too-many-pages.patch
from
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.7/2.6.7-mm2/broken-out/,
 maybe you will find out something.

Comparing the abs-fix patches from mm1 and mm2 might also help.

This is all I can do for now.

Regards 

David


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [Problem] slow write to dvd-ram since 2.6.7-bk8

2005-02-14 Thread Droebbel
On Mo, 2005-02-14 at 11:53 +0100, Tino Keitel wrote:
>On Mon, Feb 14, 2005 at 11:25:34 +0100, Droebbel wrote:
>> Which 2.6.7 did you use? 
>
>Only 2.6.7 with a -mm patch, since vanilla 2.6.7 screwed up my system
>clock, and the noapic option which was suggested to unscrew the clock
>screwed up the USB driver etc... :-(

Which -mm patch? If that patch contains the error, the bk8 contains it 
as well and the bk7 doesn't, that might already make serching a bit
easier. Or maybe 2.6.6, if you want a stable release. Not tested yet.

>What kernels do you suggest me to test?
You might try the last working one, 2.6.7 with bk7. You might as well
have to replace the drivers/cdrom/cdrom.c with on from a later virsion
(>bk15), as the cdrom device is generally marked write-protected with
bk2 to bk14.
But instead of just trying those kernel versions, I think we might try
and find the changes that might have had the unfortunate side effect. I
am admittedly not too good at that, as I do not even know C (shame on
me).

>And what test procedure? Thisis what I do in such cases:
>
>time { dd if=/dev/zero of= bs=1024k count= ; sync ; }
This is what I did.

>I'd be very happy to see a fix for this since backups to DVD-RAM are
>awfully slow at the moment.
I've been after this for months now, before finally posting here...

Regards

David

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [Problem] slow write to dvd-ram since 2.6.7-bk8

2005-02-14 Thread Droebbel
On Mo, 2005-02-14 at 09:53 +0100, Tino Keitel wrote:
>I also have low write performance (around 300 kb/s) with several 2.6
>kernels (2.6.7 to 2.6.9-mm1) and I can hear the head jump around when I
>use ext2 or UDF. It will be fast when written directly to the device
>without a file system using dd.  The drive is a LG GSA-4040B. I tried
>several media types from Panasonic and EMTEC.
>
>I'll try to test if the problem disappears with 2.6.6.

I had also tested writing with dd (forgot to mention), it seemed faster
sometimes, but not as fast as it could be. pre-2.6.7-bk8 was still
faster, though only about 25%.

Which 2.6.7 did you use? 

Regards
David

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [Problem] slow write to dvd-ram since 2.6.7-bk8

2005-02-14 Thread Tino Keitel
On Sun, Feb 13, 2005 at 09:26:35 -0500, Wakko Warner wrote:
> Droebbel wrote:
> > On recent kernels, writing to DVD-RAM is much slower than to be
> > expected. A 3x Writer should do about 1.9MB/s including automatic
> > verify. This is what I get with 2.6.7 up to bk7. However, from 2.6.7-bk8
> > to 2.6.10 write speed is as low as 600 to 1000 kB/s. The drive's head
> > jumps a lot more with these kernels. Reading is ok.
> > 
> > I tested UDF and ext2 filesystems,
> > DMA is ok according to hdparm,
> > I set taskfile-io on and off when building the kernels,
> > and I compared the settings for the io-scheduler.
> > 
> > The drive is connected via onboard via82xx ide or usb2 external (both
> > works perfectly with hd).
> > 
> > The drive is a LG GSA-4163B; a GSA-4120 had the same problem as far as I
> > remember.
> > 
> > Medium: Panasonic 3x
> > 
> > Could not find any kernel error messages.
> 
> I have:
> Host: scsi1 Channel: 00 Id: 00 Lun: 00
>   Vendor: HL-DT-ST Model: DVDRAM GSA-4160B Rev: A300
>   Type:   CD-ROM   ANSI SCSI revision: 02
> 
> I also notice this with 2.6.10.  I think I also had it with 2.6.8.1 but I
> don't remember, it's been a while.  The media I use is maxell DRM47 ver 2

I also have low write performance (around 300 kb/s) with several 2.6
kernels (2.6.7 to 2.6.9-mm1) and I can hear the head jump around when I
use ext2 or UDF. It will be fast when written directly to the device
without a file system using dd.  The drive is a LG GSA-4040B. I tried
several media types from Panasonic and EMTEC.

I'll try to test if the problem disappears with 2.6.6.

Regards,
Tino
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [Problem] slow write to dvd-ram since 2.6.7-bk8

2005-02-13 Thread Wakko Warner
Droebbel wrote:
> On recent kernels, writing to DVD-RAM is much slower than to be
> expected. A 3x Writer should do about 1.9MB/s including automatic
> verify. This is what I get with 2.6.7 up to bk7. However, from 2.6.7-bk8
> to 2.6.10 write speed is as low as 600 to 1000 kB/s. The drive's head
> jumps a lot more with these kernels. Reading is ok.
> 
> I tested UDF and ext2 filesystems,
> DMA is ok according to hdparm,
> I set taskfile-io on and off when building the kernels,
> and I compared the settings for the io-scheduler.
> 
> The drive is connected via onboard via82xx ide or usb2 external (both
> works perfectly with hd).
> 
> The drive is a LG GSA-4163B; a GSA-4120 had the same problem as far as I
> remember.
> 
> Medium: Panasonic 3x
> 
> Could not find any kernel error messages.

I have:
Host: scsi1 Channel: 00 Id: 00 Lun: 00
  Vendor: HL-DT-ST Model: DVDRAM GSA-4160B Rev: A300
  Type:   CD-ROM   ANSI SCSI revision: 02

I also notice this with 2.6.10.  I think I also had it with 2.6.8.1 but I
don't remember, it's been a while.  The media I use is maxell DRM47 ver 2
(whatever that means).  I don't notice any jumping, but the system is quite
noisy as it is.  I have this same drive at work in a usb2 box but haven't
had the opportunity to try dvdram.

The DVDRAM above is not using ide-scsi emulation, it has a hardware scsi-ide
converter from Acard.  (I already have my ide ports used).  The scsi
controller is an adaptec dual u320 onboard (supermicro x5da8)

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


[Problem] slow write to dvd-ram since 2.6.7-bk8

2005-02-13 Thread Droebbel
On recent kernels, writing to DVD-RAM is much slower than to be
expected. A 3x Writer should do about 1.9MB/s including automatic
verify. This is what I get with 2.6.7 up to bk7. However, from 2.6.7-bk8
to 2.6.10 write speed is as low as 600 to 1000 kB/s. The drive's head
jumps a lot more with these kernels. Reading is ok.

I tested UDF and ext2 filesystems,
DMA is ok according to hdparm,
I set taskfile-io on and off when building the kernels,
and I compared the settings for the io-scheduler.

The drive is connected via onboard via82xx ide or usb2 external (both
works perfectly with hd).

The drive is a LG GSA-4163B; a GSA-4120 had the same problem as far as I
remember.

Medium: Panasonic 3x

Could not find any kernel error messages.


For testing the 2.6.7-bk2 to bk14 I took the cdrom.c from bk15, as the
cdrom devices wer marked read-only without.


As I am not a programmer, I failed to track down the problem any
further, but I'll do my best if I get any hints or advice where to
search.

David

--

**hdparm output:**

 Model=HL-DT-ST DVDRAM GSA-4163B, FwRev=A101, SerialNo=K764C241904
 Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
 RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
 BuffType=unknown, BuffSize=0kB, MaxMultSect=0
 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio3 pio4
 DMA modes:  mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 *udma2
 AdvancedPM=no
 Drive conforms to: device does not report version:

 * signifies the current active mode


ATAPI CD-ROM, with removable media
Model Number:   HL-DT-ST DVDRAM GSA-4163B
Serial Number:  K764C241904
Firmware Revision:  A101
Standards:
Likely used CD-ROM ATAPI-1
Configuration:
DRQ response: 50us.
Packet size: 12 bytes
Capabilities:
LBA, IORDY(can be disabled)
DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2
 Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
 Cycle time: no flow control=120ns  IORDY flow control=120ns
HW reset results:
CBLID- above Vih
Device num = 0

-

Additional information:
**Output of ver_linux on the testing system with 2.6.7-bk8:**

Linux schlupp 2.6.7-bk8 #6 Sat Feb 12 22:28:31 CET 2005 i686 GNU/Linux

Gnu C  3.3.5
Gnu make   3.80
binutils   2.15
util-linux 2.12p
mount  2.12p
module-init-tools  3.1
e2fsprogs  1.35
jfsutils   1.1.6
xfsprogs   2.6.20
PPP2.4.2
Linux C Library2.3.2
Dynamic linker (ldd)   2.3.2
Procps 3.2.4
Net-tools  1.60
Console-tools  0.2.3
Sh-utils   5.2.1
Modules Loaded ehci_hcd uhci_hcd sata_via libata md dm_mod
parport_pc lp parport sr_mod

---

**ioports**

-001f : dma1
0020-0021 : pic1
0040-005f : timer
0060-006f : keyboard
0070-0077 : rtc
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
02f8-02ff : serial
0376-0376 : ide1
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial
0808-080b : ACPI timer
0810-0815 : ACPI CPU throttle
0cf8-0cff : PCI conf1
b000-b0ff : :00:0e.0
b400-b407 : :00:0e.0
b800-b81f : :00:10.0
  b800-b81f : uhci_hcd
c000-c01f : :00:10.1
  c000-c01f : uhci_hcd
c400-c41f : :00:10.2
  c400-c41f : uhci_hcd
c800-c81f : :00:10.3
  c800-c81f : uhci_hcd
cc00-cc7f : :00:07.0
d000-d0ff : :00:0f.0
  d000-d0ff : sata_via
d400-d40f : :00:0f.0
  d400-d40f : sata_via
d800-d803 : :00:0f.0
  d800-d803 : sata_via
dc00-dcff : :00:0a.0
e000-e007 : :00:0f.0
  e000-e007 : sata_via
e400-e403 : :00:0f.0
  e400-e403 : sata_via
e800-e807 : :00:0f.0
  e800-e807 : sata_via
ec00-ecff : :00:0c.0
fc00-fc0f : :00:0f.1
  fc00-fc07 : ide0
  fc08-fc0f : ide1

-

**iomem**

-0009fbff : System RAM
0009fc00-0009 : reserved
000a-000b : Video RAM area
000c-000cb7ff : Video ROM
000f-000f : System ROM
0010-1ff2 : System RAM
  0010-0035f07d : Kernel code
  0035f07e-004413ff : Kernel data
1ff3-1ff3 : ACPI Tables
1ff4-1ffe : ACPI Non-volatile Storage
1fff-1fff : reserved
e4e0-f4df : PCI Bus #01
  e800-efff : :01:00.0
f4f0-f70f : PCI Bus #01
  f600-f6ff : :01:00.0
f770-f77007ff : :00:07.0
f7b0-f7b03fff : :00:0a.0
f7d0-f7d000ff : :00:0c.0
f7e0-f7e000ff : :00:0e.0
f7f0-f7f000ff : :00:10.4
  f7f0-f7f000ff : ehci_hcd
f800-fbff : :00:00.0
fff8- : reserved

-

**lspci**

:00:00.0 Host bridge: VIA Technologies, Inc. VT8385 [K8T800 AGP]
Host Bridge (rev 01)
Subsystem: Asustek Computer, Inc.: Unknown device 80a3
Control: I/O- Mem+ BusMas

Re: write to dvd ram

2001-05-23 Thread Helge Hafting

[EMAIL PROTECTED] wrote:
> 
> OK, I've asked this question four weeks in a row and received no response 
>whatsoever.  
This happens.  So what?  Nobody _promised_ you anything.
> Linux is supposed to be the OS where you can turn to the newsgroups/IRC and get able 
>help.
Linux is the os where you often, but not necessarily will get help form
newsgroups and mailinglists.  Particularly, try finding the _right_
list.
 
> This is to those who couldn't lift a finger to help with this compile/driver problem:
Why would anyone lift a finger for you?  Did _you_ ever help someone?
I (and many others) couldn't help because we don't know anything about
your driver and havent used UDF.  Seek out those few who knows.
> Thanks for nothing, you arrogant snots.  You don't know how much damage you do.

Damage?  Nobody did any damage by not helping you.  That's impossible
per definition.  There are tasks for which linux aren't ready, maybe you
found one of them.

Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: write to dvd ram

2001-05-22 Thread Rafael Herrera

I tried to give you some pointers in a personal email. So it's not true
you didn't receive any response. Also reminded you of the best place to
look for info, namely, that driver's mailing list. You don't seem to
have made any additional attempts at resolving it yourself since you
reposted your original message. Get newer kernel sources, read the
driver's documentation more thoroughly.
-- 
 Rafael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: write to dvd ram

2001-05-22 Thread David Weinehall

On Tue, May 22, 2001 at 10:38:49AM -0600, [EMAIL PROTECTED] wrote:
> OK, I've asked this question four weeks in a row and received no response
> whatsoever.  Linux is supposed to be the OS where you can turn to the
> newsgroups/IRC and get able help.
> 
> This is to those who couldn't lift a finger to help with this compile/driver
> problem:

Ignoring your obvious attitude problem for now (you haven't ever
considered the fact that (almost) all the people on this list develop
Linux voluntarily, in their spare-time?!), I suggest you try
at #kernelnewbies on irc if you want response. Or you could try to
download a newer version of the kernel. You know, the bug might've been
fixed since v2.4.2...


/David Weinehall
  _ _
 // David Weinehall <[EMAIL PROTECTED]> /> Northern lights wander  \\
//  Project MCA Linux hacker//  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: write to dvd ram

2001-05-22 Thread cacook

OK, I've asked this question four weeks in a row and received no response whatsoever.  
Linux is supposed to be the OS where you can turn to the newsgroups/IRC and get able 
help.

This is to those who couldn't lift a finger to help with this compile/driver problem:
Thanks for nothing, you arrogant snots.  You don't know how much damage you do.



 Original Message ----
Subject: Re: write to dvd ram
Date: Tue, 15 May 2001 10:32:21 -0600
From: @.
To: [EMAIL PROTECTED]

No one has a minute to help me with this (compile?) problem?  Linus ?





 Original Message ----
Subject: Re: write to dvd ram
Date: Fri, 11 May 2001 07:57:56 -0600
From: @.
To: [EMAIL PROTECTED]
References: <91FD33983070D21188A10008C728176C09421202@LDMS6003> 
<[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>

Only udf I could find that was compatible with kernel 2.4.2 was the udf-0.9.3 tarball. 
 It does have a 2.4 directory.  I am restricted in which kernel I can use, as I must 
have a patch for fibrechannel.  My compile craps out with the listing below; I can't 
make any sense out of it.

I have used Linux for several years as my firewall, and in December 2k I decided to 
make it my workstation.  Since that time I have worked on configuring it at least a 
few hours each workday afternoon. (RedHat Fisher, then Wolverine)  Now I am not a 
dummy, but I'm not a coder either, and I have just not been able to get this system 
running, and am now up against two problems I cannot solve: this DVDRAM | UDF issue 
corrupting my disks (Why is udf-0.9.1 in Wolverine, wrecking my DVDRAM data?  And how 
can I install udf as a module when it's already in kernel?), and Wine setup.  No one 
has
answered my questions on the kernel IRCs nor Wine mailinglist -- they're fairly cross 
with newbies who have actually  read/followed the docs.  Often when I ask a question I 
get taken down like an elk by a lion.  This isn't supposed to be natural selection 
people.  Supposed to =bring= ppl to Linux;  don't they know the damage they do to 
Linux by blowing off their steam?  Most newbies won't slap them back down;  they'll 
just go away quietly & then put down Linux to others.

I haven't even yet gotten to learning/configuring Sane, LDAP, Postfix, IPTables, VPN, 
nor intrusion detection, much less database & production functions.

I just don't know how I'm going to make this work =practically=  as much as I want it; 
 RedHat just seems to require unlimited volumes of time.  After months I am precisely 
nowhere, and stuck with Windows, and discouraged; looks like I have at least another 
year of =configuring= at this rate.
--
C.

The best way out is always through.
  - Robert Frost  A Servant to Servants, 1914


Linux UDF Configuration Script

The default responses for each question are correct for most users.

Linux source directory [/usr/src/linux]: /usr/src/linux-2.4.2-temp
Alternate target install directory []: /lib/modules/2.4.2-0.1.49
C compiler name [gcc]:
Linker name [ld -m elf_i386]:
UDF Write Support (y/n) [y]:
Compiler flags for debugging [-g]:

The UDF driver needs to be compiled to match the kernel it will be used with, or it 
may fail to load.  If you are not sure what to do, please consult the UDF manual.

How would you like to set kernel-specific options?
1 - Read from the currently running kernel
2 - Read from the Linux source tree
Enter option (1-2) [1]: 2

Kernel configuration options:
Symmetric multiprocessing support is disabled.
Max physical memory in MB is
Advanced Power Management (APM) support is enabled.
Networking support is enabled.
Module version checking is enabled.

The kernel source tree is version 2.4.2-0.1.49.
The current kernel build date is Wed Apr 18 20:53:37 MDT 2001.

Your module utilities are version 2.4.2.
make[1]: Entering directory `/usr/send-rec/download/udf-0.9.3/module'
gcc -MD -O2 -Wall -Wstrict-prototypes -pipe -DMODVERSIONS -include 
/usr/src/linux-2.4.2-temp/include/linux/modversions.h -g -D__KERNEL__ -DMODULE 
-I../include -I. -I/usr/src/linux-2.4.2-temp/include  -DUDFFS_RW=1 -DCONFIG_UDF_FS_EXT 
-c -o balloc.o ../linux-2.4/balloc.c
../linux-2.4/balloc.c:115:17: warning: pasting "(" and ""block_group (%d) > nr_groups 
(%d)\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:160:17: warning: pasting "(" and ""nonexistent device"" does not 
give a valid preprocessing token
../linux-2.4/balloc.c:168:17: warning: pasting "(" and ""%d < %d || %d + %d > %d\n"" 
does not give a valid preprocessing token
../linux-2.4/balloc.c:198:25: warning: pasting "(" and ""bit %ld already set\n"" does 
not give a valid preprocessing token
../linux-2.4/balloc.c:199:25: warning: pasting "(" and ""byte=%2x\

Re: write to dvd ram

2001-05-22 Thread quantum7

OK, I've asked this question four weeks in a row and received no response whatsoever.  
Linux is supposed to be the OS where you can turn to the newsgroups/IRC and get able 
help.

This is to those who couldn't lift a finger to help with this compile/driver problem:
Thanks for nothing, you arrogant snots.  You don't know how much damage you do.



 Original Message ----
Subject: Re: write to dvd ram
Date: Tue, 15 May 2001 10:32:21 -0600
From: @.
To: [EMAIL PROTECTED]

No one has a minute to help me with this (compile?) problem?  Linus ?





 Original Message ----
Subject: Re: write to dvd ram
Date: Fri, 11 May 2001 07:57:56 -0600
From: @.
To: [EMAIL PROTECTED]
References: <91FD33983070D21188A10008C728176C09421202@LDMS6003> 
<[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>

Only udf I could find that was compatible with kernel 2.4.2 was the udf-0.9.3 tarball. 
 It does have a 2.4 directory.  I am restricted in which kernel I can use, as I must 
have a patch for fibrechannel.  My compile craps out with the listing below; I can't 
make any sense out of it.

I have used Linux for several years as my firewall, and in December 2k I decided to 
make it my workstation.  Since that time I have worked on configuring it at least a 
few hours each workday afternoon. (RedHat Fisher, then Wolverine)  Now I am not a 
dummy, but I'm not a coder either, and I have just not been able to get this system 
running, and am now up against two problems I cannot solve: this DVDRAM | UDF issue 
corrupting my disks (Why is udf-0.9.1 in Wolverine, wrecking my DVDRAM data?  And how 
can I install udf as a module when it's already in kernel?), and Wine setup.  No one 
has
answered my questions on the kernel IRCs nor Wine mailinglist -- they're fairly cross 
with newbies who have actually  read/followed the docs.  Often when I ask a question I 
get taken down like an elk by a lion.  This isn't supposed to be natural selection 
people.  Supposed to =bring= ppl to Linux;  don't they know the damage they do to 
Linux by blowing off their steam?  Most newbies won't slap them back down;  they'll 
just go away quietly & then put down Linux to others.

I haven't even yet gotten to learning/configuring Sane, LDAP, Postfix, IPTables, VPN, 
nor intrusion detection, much less database & production functions.

I just don't know how I'm going to make this work =practically=  as much as I want it; 
 RedHat just seems to require unlimited volumes of time.  After months I am precisely 
nowhere, and stuck with Windows, and discouraged; looks like I have at least another 
year of =configuring= at this rate.
--
C.

The best way out is always through.
  - Robert Frost  A Servant to Servants, 1914


Linux UDF Configuration Script

The default responses for each question are correct for most users.

Linux source directory [/usr/src/linux]: /usr/src/linux-2.4.2-temp
Alternate target install directory []: /lib/modules/2.4.2-0.1.49
C compiler name [gcc]:
Linker name [ld -m elf_i386]:
UDF Write Support (y/n) [y]:
Compiler flags for debugging [-g]:

The UDF driver needs to be compiled to match the kernel it will be used with, or it 
may fail to load.  If you are not sure what to do, please consult the UDF manual.

How would you like to set kernel-specific options?
1 - Read from the currently running kernel
2 - Read from the Linux source tree
Enter option (1-2) [1]: 2

Kernel configuration options:
Symmetric multiprocessing support is disabled.
Max physical memory in MB is
Advanced Power Management (APM) support is enabled.
Networking support is enabled.
Module version checking is enabled.

The kernel source tree is version 2.4.2-0.1.49.
The current kernel build date is Wed Apr 18 20:53:37 MDT 2001.

Your module utilities are version 2.4.2.
make[1]: Entering directory `/usr/send-rec/download/udf-0.9.3/module'
gcc -MD -O2 -Wall -Wstrict-prototypes -pipe -DMODVERSIONS -include 
/usr/src/linux-2.4.2-temp/include/linux/modversions.h -g -D__KERNEL__ -DMODULE 
-I../include -I. -I/usr/src/linux-2.4.2-temp/include  -DUDFFS_RW=1 -DCONFIG_UDF_FS_EXT 
-c -o balloc.o ../linux-2.4/balloc.c
../linux-2.4/balloc.c:115:17: warning: pasting "(" and ""block_group (%d) > nr_groups 
(%d)\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:160:17: warning: pasting "(" and ""nonexistent device"" does not 
give a valid preprocessing token
../linux-2.4/balloc.c:168:17: warning: pasting "(" and ""%d < %d || %d + %d > %d\n"" 
does not give a valid preprocessing token
../linux-2.4/balloc.c:198:25: warning: pasting "(" and ""bit %ld already set\n"" does 
not give a valid preprocessing token
../linux-2.4/balloc.c:199:25: warning: pasting "(" and ""byte=%2x\

Re: write to dvd ram

2001-05-15 Thread cacook

No one has a minute to help me with this (compile?) problem?  Linus ?





 Original Message 
Subject: Re: write to dvd ram
Date: Fri, 11 May 2001 07:57:56 -0600
From: @.
To: [EMAIL PROTECTED]
References: <91FD33983070D21188A10008C728176C09421202@LDMS6003> 
<[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>

Only udf I could find that was compatible with kernel 2.4.2 was the udf-0.9.3 tarball. 
 It does have a 2.4 directory.  I am restricted in which kernel I can use, as I must 
have a patch for fibrechannel.  My compile craps out with the listing below; I can't 
make any sense out of it.

I have used Linux for several years as my firewall, and in December 2k I decided to 
make it my workstation.  Since that time I have worked on configuring it at least a 
few hours each workday afternoon. (RedHat Fisher, then Wolverine)  Now I am not a 
dummy, but I'm not a coder either, and I have just not been able to get this system 
running, and am now up against two problems I cannot solve: this DVDRAM | UDF issue 
corrupting my disks (Why is udf-0.9.1 in Wolverine, wrecking my DVDRAM data?  And how 
can I install udf as a module when it's already in kernel?), and Wine setup.  No one 
has
answered my questions on the kernel IRCs nor Wine mailinglist -- they're fairly cross 
with newbies who have actually  read/followed the docs.  Often when I ask a question I 
get taken down like an elk by a lion.  This isn't supposed to be natural selection 
people.  Supposed to =bring= ppl to Linux;  don't they know the damage they do to 
Linux by blowing off their steam?  Most newbies won't slap them back down;  they'll 
just go away quietly & then put down Linux to others.

I haven't even yet gotten to learning/configuring Sane, LDAP, Postfix, IPTables, VPN, 
nor intrusion detection, much less database & production functions.

I just don't know how I'm going to make this work =practically=  as much as I want it; 
 RedHat just seems to require unlimited volumes of time.  After months I am precisely 
nowhere, and stuck with Windows, and discouraged; looks like I have at least another 
year of =configuring= at this rate.
--
C.

The best way out is always through.
  - Robert Frost  A Servant to Servants, 1914


Linux UDF Configuration Script

The default responses for each question are correct for most users.

Linux source directory [/usr/src/linux]: /usr/src/linux-2.4.2-temp
Alternate target install directory []: /lib/modules/2.4.2-0.1.49
C compiler name [gcc]:
Linker name [ld -m elf_i386]:
UDF Write Support (y/n) [y]:
Compiler flags for debugging [-g]:

The UDF driver needs to be compiled to match the kernel it will be used with, or it 
may fail to load.  If you are not sure what to do, please consult the UDF manual.

How would you like to set kernel-specific options?
1 - Read from the currently running kernel
2 - Read from the Linux source tree
Enter option (1-2) [1]: 2

Kernel configuration options:
Symmetric multiprocessing support is disabled.
Max physical memory in MB is
Advanced Power Management (APM) support is enabled.
Networking support is enabled.
Module version checking is enabled.

The kernel source tree is version 2.4.2-0.1.49.
The current kernel build date is Wed Apr 18 20:53:37 MDT 2001.

Your module utilities are version 2.4.2.
make[1]: Entering directory `/usr/send-rec/download/udf-0.9.3/module'
gcc -MD -O2 -Wall -Wstrict-prototypes -pipe -DMODVERSIONS -include 
/usr/src/linux-2.4.2-temp/include/linux/modversions.h -g -D__KERNEL__ -DMODULE 
-I../include -I. -I/usr/src/linux-2.4.2-temp/include  -DUDFFS_RW=1 -DCONFIG_UDF_FS_EXT 
-c -o balloc.o ../linux-2.4/balloc.c
../linux-2.4/balloc.c:115:17: warning: pasting "(" and ""block_group (%d) > nr_groups 
(%d)\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:160:17: warning: pasting "(" and ""nonexistent device"" does not 
give a valid preprocessing token
../linux-2.4/balloc.c:168:17: warning: pasting "(" and ""%d < %d || %d + %d > %d\n"" 
does not give a valid preprocessing token
../linux-2.4/balloc.c:198:25: warning: pasting "(" and ""bit %ld already set\n"" does 
not give a valid preprocessing token
../linux-2.4/balloc.c:199:25: warning: pasting "(" and ""byte=%2x\n"" does not give a 
valid preprocessing token
../linux-2.4/balloc.c:203:54: macro "DQUOT_FREE_BLOCK" passed 3 arguments, but takes 
just 2
../linux-2.4/balloc.c:239:17: warning: pasting "(" and ""nonexistent device\n"" does 
not give a valid preprocessing token
../linux-2.4/balloc.c:268:59: macro "DQUOT_PREALLOC_BLOCK" passed 3 arguments, but 
takes just 2
../linux-2.4/balloc.c:272:25: warning: pasting "(" and ""bi

Re: write to dvd ram

2001-05-11 Thread cacook

Only udf I could find that was compatible with kernel 2.4.2 was the udf-0.9.3 tarball. 
 It does have a 2.4 directory.  I am restricted in which kernel I can use, as I must 
have a patch for fibrechannel.  My compile craps out with the listing below; I can't 
make any sense out of it.

I have used Linux for several years as my firewall, and in December 2k I decided to 
make it my workstation.  Since that time I have worked on configuring it at least a 
few hours each workday afternoon. (Fisher, then Wolverine)  Now I am not a dummy, but 
I'm not a coder either, and I have just not been able to get this system running, and 
am now up against two problems I cannot solve: this DVDRAM | UDF issue corrupting my 
disks (Why is udf-0.9.1 in Wolverine, wrecking my DVDRAM data?  And how can I install 
udf as a module when it's already in kernel?), and Wine setup.  No one has answered my
questions on the kernel IRCs nor Wine mailinglist -- they're fairly cross with newbies 
who have actually  read/followed the docs.  Often when I ask a question I get taken 
down like an elk by a lion.  This isn't supposed to be natural selection people.  
Supposed to =bring= ppl to Linux;  don't they know the damage they do to Linux by 
blowing off their steam?  Most newbies won't slap them back down;  they'll just go 
away quietly & then put down Linux to others.

I haven't even yet gotten to learning/configuring Sane, LDAP, Postfix, IPTables, VPN, 
nor intrusion detection, much less database.

I just don't know how I'm going to make this work =practically=  as much as I want it; 
 RedHat just seems to require unlimited volumes of time.  After months I am precisely 
nowhere, and stuck with Windows, and discouraged; looks like I have at least another 
year of =configuring= at this rate.
--
C.

The best way out is always through.
  - Robert Frost  A Servant to Servants, 1914


Linux UDF Configuration Script

The default responses for each question are correct for most users.

Linux source directory [/usr/src/linux]: /usr/src/linux-2.4.2-temp
Alternate target install directory []: /lib/modules/2.4.2-0.1.49
C compiler name [gcc]:
Linker name [ld -m elf_i386]:
UDF Write Support (y/n) [y]:
Compiler flags for debugging [-g]:

The UDF driver needs to be compiled to match the kernel it will be used with, or it 
may fail to load.  If you are not sure what to do, please consult the UDF manual.

How would you like to set kernel-specific options?
1 - Read from the currently running kernel
2 - Read from the Linux source tree
Enter option (1-2) [1]: 2

Kernel configuration options:
Symmetric multiprocessing support is disabled.
Max physical memory in MB is
Advanced Power Management (APM) support is enabled.
Networking support is enabled.
Module version checking is enabled.

The kernel source tree is version 2.4.2-0.1.49.
The current kernel build date is Wed Apr 18 20:53:37 MDT 2001.

Your module utilities are version 2.4.2.
make[1]: Entering directory `/usr/send-rec/download/udf-0.9.3/module'
gcc -MD -O2 -Wall -Wstrict-prototypes -pipe -DMODVERSIONS -include 
/usr/src/linux-2.4.2-temp/include/linux/modversions.h -g -D__KERNEL__ -DMODULE 
-I../include -I. -I/usr/src/linux-2.4.2-temp/include  -DUDFFS_RW=1 -DCONFIG_UDF_FS_EXT 
-c -o balloc.o ../linux-2.4/balloc.c
../linux-2.4/balloc.c:115:17: warning: pasting "(" and ""block_group (%d) > nr_groups 
(%d)\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:160:17: warning: pasting "(" and ""nonexistent device"" does not 
give a valid preprocessing token
../linux-2.4/balloc.c:168:17: warning: pasting "(" and ""%d < %d || %d + %d > %d\n"" 
does not give a valid preprocessing token
../linux-2.4/balloc.c:198:25: warning: pasting "(" and ""bit %ld already set\n"" does 
not give a valid preprocessing token
../linux-2.4/balloc.c:199:25: warning: pasting "(" and ""byte=%2x\n"" does not give a 
valid preprocessing token
../linux-2.4/balloc.c:203:54: macro "DQUOT_FREE_BLOCK" passed 3 arguments, but takes 
just 2
../linux-2.4/balloc.c:239:17: warning: pasting "(" and ""nonexistent device\n"" does 
not give a valid preprocessing token
../linux-2.4/balloc.c:268:59: macro "DQUOT_PREALLOC_BLOCK" passed 3 arguments, but 
takes just 2
../linux-2.4/balloc.c:272:25: warning: pasting "(" and ""bit already cleared for
 block %d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:273:54: macro "DQUOT_FREE_BLOCK" passed 3 arguments, but takes 
just 2
../linux-2.4/balloc.c:310:17: warning: pasting "(" and ""nonexistent device\n""
does not give a valid preprocessing token
../linux-2.4/balloc.c:407:43: macro "DQUOT_ALLOC_BLOCK" passed 3 arguments, but takes 
just 2
../linux-2.4/balloc.c:420:17: warning: pasting "(" and ""bit already cleared for
 block %d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:454:9: warning: pasting "(" and ""ino=%ld, bloc=%d, offset
=%d, count=%d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:460

Re: write to dvd ram

2001-05-08 Thread Jens Axboe

On Tue, May 08 2001, Thiago Vinhas de Moraes wrote:
> 
> Hi!
> 
> Can this new UDF driver do cd-rewriting ?

No not in itself, but you can give the pktcdvd module a shot. It can do
rw CD-RW mount so far, at least.

*.kernel.org/pub/linux/kernel/people/axboe/packet/

There's a packet-writing mailing list for the above patch, there is more
info in the tar file above (subscribe info, archives, resources, etc).

-- 
Jens Axboe

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: write to dvd ram

2001-05-08 Thread Thiago Vinhas de Moraes


Hi!

Can this new UDF driver do cd-rewriting ?



Em Ter 08 Mai 2001 14:50, Jens Axboe escreveu:
> On Tue, May 08 2001, Ben Fennema wrote:
> > > The log is:
> > > Apr 15 20:58:27 hydra kernel: UDF-fs INFO UDF 0.9.1 (2000/02/29)
> > > Mounting volume 'UDF Volume', timestamp 2001/03/02 11:55 (1e98)
> >
> > At the very least, run 0.9.3 from sourceforce (or the cvs version) and
> > see if it works any better.
>
> I was just about to say the same thing, 0.9.3 works well for me. In fact
> so well, that I made a patch to bring 2.4.5-pre1 UDF up to date with
> current CVS earlier this afternoon (hint hint, Ben :-).
>
> *.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.5-pre1/
>
> udf-0.9.3-2.4.5p1-1.bz2

-- 

 Thiago Vinhas de Moraes
 NetWorx - A SuaCompanhia.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: write to dvd ram

2001-05-08 Thread cacook

Thanks, I'll try it.  Didn't get the prior response.
--
C.

The best way out is always through.
  - Robert Frost  A Servant to Servants, 1914



Jens Axboe wrote:

> On Tue, May 08 2001, Ben Fennema wrote:
> > > The log is:
> > > Apr 15 20:58:27 hydra kernel: UDF-fs INFO UDF 0.9.1 (2000/02/29) Mounting
> > > volume 'UDF Volume', timestamp 2001/03/02 11:55 (1e98)
> >
> > At the very least, run 0.9.3 from sourceforce (or the cvs version) and
> > see if it works any better.
>
> I was just about to say the same thing, 0.9.3 works well for me. In fact
> so well, that I made a patch to bring 2.4.5-pre1 UDF up to date with
> current CVS earlier this afternoon (hint hint, Ben :-).
>
> *.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.5-pre1/
>
> udf-0.9.3-2.4.5p1-1.bz2
>
> --
> Jens Axboe




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: write to dvd ram

2001-05-08 Thread Jens Axboe

On Tue, May 08 2001, Ben Fennema wrote:
> > The log is:
> > Apr 15 20:58:27 hydra kernel: UDF-fs INFO UDF 0.9.1 (2000/02/29) Mounting
> > volume 'UDF Volume', timestamp 2001/03/02 11:55 (1e98)
> 
> At the very least, run 0.9.3 from sourceforce (or the cvs version) and
> see if it works any better.

I was just about to say the same thing, 0.9.3 works well for me. In fact
so well, that I made a patch to bring 2.4.5-pre1 UDF up to date with
current CVS earlier this afternoon (hint hint, Ben :-).

*.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.5-pre1/

udf-0.9.3-2.4.5p1-1.bz2

-- 
Jens Axboe

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: write to dvd ram

2001-05-08 Thread Ben Fennema

> The log is:
> Apr 15 20:58:27 hydra kernel: UDF-fs INFO UDF 0.9.1 (2000/02/29) Mounting
> volume 'UDF Volume', timestamp 2001/03/02 11:55 (1e98)

At the very least, run 0.9.3 from sourceforce (or the cvs version) and
see if it works any better.

Ben
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: write to dvd ram

2001-05-08 Thread cacook

Many thanks Jim.  Now at least I have a way.

But I caution others that Linux modifies the UDF filesystem somehow, so that Winders 
can no longer understand it.  I nearly lost all my music & photo archives to this.  
And attempts to rm or mv on a DVDRAM with UDF cause it to segfault & jam up.  There 
doesn't seem to be an answer to this.  (yes, I have written to the developer of 
cddriver; no response at all after two weeks)  UDF2 is just nonfunctional in Linux and 
I don't know why.

To recap: running Panasonic LF-D101 DVDRAM drive on SCSI (AHA2940) and
getting segfaults.  On-disk format is UDF2.0, as 2.1 won't mount.

Mount, ls, umount, mount, ls, umount, etc - no problem except filestructure is now no 
longer available to Winders. (CAUTION! Save data using Linux for recovery in Winders)

Mount, cp <20Mfile>, umount, mount, ls, (20Mfile), umount, mount, ls, (20Mfile),
rpm -q 20Mfile, umount, etc - no problem except filestructure no longer available to 
Winders.

Mount, rm <20Mfile>, Segmentation Fault, umount, (device busy), umount, (device busy), 
etc.  Reboot without reset and bootup hangs at Running Linuxconf hooks. Reset & system 
boots fine.  Mount, ls, (no files), umount, mount, ls, (no files), umount, etc.

Running RedHat Wolverine with HelixGnome & Nautilus.
--
C.

The best way out is always through.
  - Robert Frost  A Servant to Servants, 1914

Keywords: DVDRAM DVD-RAM LF-D101 LFD101 cdrecord


The log is:
Apr 15 20:58:27 hydra kernel: UDF-fs INFO UDF 0.9.1 (2000/02/29) Mounting
volume 'UDF Volume', timestamp 2001/03/02 11:55 (1e98)
Apr 15 20:59:31 hydra kernel: UDF-fs INFO UDF 0.9.1 (2000/02/29) Mounting
volume 'UDF Volume', timestamp 2001/03/02 11:55 (1e98)
Apr 15 20:59:50 hydra last message repeated 3 times
Apr 15 21:00:17 hydra mon[1258]: failure for servers http 987390017 localhost
Apr 15 21:01:11 hydra kernel: UDF-fs INFO UDF 0.9.1 (2000/02/29) Mounting
volume 'UDF Volume', timestamp 2001/03/02 11:55 (1e98)
Apr 15 21:03:25 hydra last message repeated 2 times
Apr 15 21:03:40 hydra kernel: kernel BUG at inode.c:890!
Apr 15 21:03:40 hydra kernel: invalid operand: 
Apr 15 21:03:40 hydra kernel: CPU:0
Apr 15 21:03:40 hydra kernel: EIP:0010:[iput_free+216/352]
Apr 15 21:03:40 hydra kernel: EIP:0010:[]
Apr 15 21:03:40 hydra kernel: EFLAGS: 00010286
Apr 15 21:03:40 hydra kernel: eax: 001b   ebx: cb1ad640   ecx: 0004
edx: c5508840
Apr 15 21:03:40 hydra kernel: esi: c0319560   edi: cb4f2740   ebp: b678 esp:
c9d5ff20
Apr 15 21:03:40 hydra kernel: ds: 0018   es: 0018   ss: 0018
Apr 15 21:03:40 hydra kernel: Process rm (pid: 2254, stackpage=c9d5f000)
Apr 15 21:03:40 hydra kernel: Stack: c02a1610 c02a16f3 037a 
0012 c392 cffb3560 cb4f2740
Apr 15 21:03:40 hydra kernel:cb1ad640 c0144a3c cb1ad640 0184
fff0 c39229c0 cb4f2740 
Apr 15 21:03:40 hydra kernel:c39229c0 c013e31c cb4f2740 cfc83d40
c9d5ff9c  ffeb cb4f2740
Apr 15 21:03:40 hydra kernel: Call Trace: [error_table+39488/42452]
[error_table+39715/42452] [d_delete+76/112] [vfs_unlink+316/368]
[sys_unlink+150/272] [do_page_fault+0/1088] [system_call+51/56]
Apr 15 21:03:40 hydra kernel: Call Trace: [] []
[] [] [] [] []
Apr 15 21:03:40 hydra kernel:
Apr 15 21:03:40 hydra kernel: Code: 0f 0b 83 c4 0c eb 69 90 39 1b 74 3c f6 83 f8 00 00 
00 07 75
Apr 15 21:04:18 hydra mon[1258]: failure for servers http 987390258 localhost


ver_linux
Linux hydra.darkmatter.com 2.4.2-0.1.49 #1 Sun Apr 15 18:12:33 MDT 2001 i686 unknown

Gnu C  2.96
Gnu make   3.79.1
binutils   2.10.91.0.2
util-linux 2.10r
modutils   2.4.2
e2fsprogs  1.19
reiserfsprogs  3.x.0b
PPP2.4.0
isdn4k-utils   3.1pre1
Linux C Library2.2.2
Dynamic linker (ldd)   2.2.2
Procps 2.0.7
Net-tools  1.57
Console-tools  0.3.3
Sh-utils   2.0
Modules Loaded via82cxxx_audio ac97_codec binfmt_misc autofs
nls_iso8859-1 nls_cp437
cdrecord 1.9-6


"Hawthorne, Jim J SSI-ISEA" wrote:

> No problem with ext2 file system -- I have been using LM 7.2 with kernel
> 2.2.14 and it works straight out of the box. Newer kernel 2.4.x should also
> work .
> Have Toshiba w1101 scsi dvd ram and initio wide scsi card. I also use
> WINDOZE 2000 and use UDF for DVD RAM on WINDOZE 2000 (Instant Write from VOB
> at www.vob.de -- came with the drive).
>
> I use BRUBACK for backup to backup both Linux and W2K (Bruback will backup
> windoze filesystem from Linux -- no problem)
>
> format your media with mke2fs /dev/scd1 (or wherever your dvd ram is
> detected) -- just use defaults  takes about 1 min to format a 2.6 GB media.
>
> create a directory under /   say /dvdram
>
> then simply mount -t ext2 /dev/scd1 /dvdram  hey presto you should get
> read/write access to your drive
>
> your fstab entry should look something like this
>
> /dev/scd1 /dvdram ext2 noauto,