Disk Device Driver Semantics Question

From: Ed Mehlschau <em_at_icess.ucsb.edu>
Date: Wed, 05 Feb 97 12:25:16 -0800

DUX Gurus,

To keep a long story short, I have an ADVfs-type file system that was
not backed up. The file system was spread across a 3 9GB-drive array.
When the array started passing write errors back to the host (a
3000/800 running DUX 3.2C) the host kernel would panic, crash, and
reboot, panic, crash, and reboot, ..., ad nauseum. So I umount(8)ed
the array and used dd(1) to copy the 3 drives, block by block, out to
tapes. These copies were successful.

Now I think have my hardware problems solved, and I want to copy the
file system from tape back to disk. However, when I try to do so, for
example, with:

    dd if=/dev/nrmt1h of=/dev/rrz11c bs=1024k

I get a write error (errno == EROFS (Read-only file system)) a fraction
of a block into the copy. I've worked with many UNIX disk drivers over
the years, but I can't recall seeing one do this before. What gives?
Is the driver preventing me from scribbling over the label or
something?

Thanks!

-- Ed

----------
Interviewer: "You're a very strange man Mr. Von Bulow."
Claus Von Bulow: "You have no idea."
Received on Wed Feb 05 1997 - 21:51:35 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:47 NZDT