Stephan> On Wed, 25 Jun 2003 21:16:55 +0200
Stephan> Willy Tarreau <willy@w.ods.org> wrote:
>> Hmmm no, you're right, I forgot about this case. I think that
>> access time or other time-dependant informations may change often
>> enough to make a big diff on checksums. I have no more idea at the
>> moment. Or perhaps tar to a disk file instead of the tape and check
>> that file :-/
Stephan> I have tried that already but never managed to get
Stephan> verification errors on tar archives written to disk. Maybe I
Stephan> try again some more...
I've been trying to get tar errors myself, while writing a 35gb
filesystem to a DLT7000. I'm now running 2.4.21-pre5-ac1 and I
haven't seen any errors. Yet. I'm using the 6.2.8 version of the
driver as well. The filesystem is just a copy of my home directory
and some MP3s and other random files and such. Lots of text and jpegf
files, along with some other stuff.
Maybe I need to try and generate 15-18 files 2gb+ each and dump them
to tape with tar and see how that's handled, and if we get erorrs.
Stephan, can you double check your version info as well? And it would
be great to get some info on your 3ware setup as well, just so we can
work on narrowing down the issues.
Unfortunately, due to the way I have to setup things, the RAID array
and the tape drive are on the same channel, which slows down things
I'm sure.
Here are some timings from dumping and verifying the data to tape:
jfsnew:/# time tar -c-W -b 128 -f /dev/st0 /scratch
tar: Removing leading `/' from member names
408.840u 869.730s 4:03:02.80 8.7% 0+0k 0+0io 258pf+0w
jfsnew:/# time tar -c-W -b 256 -f /dev/st0 /scratch
tar: Removing leading `/' from member names
443.210u 1104.930s 4:07:00.89 10.4% 0+0k 0+0io 264pf+0w
My filesystem is a as follows:
jfsnew:/home# mdadm -D /dev/md1
/dev/md1:
Version : 00.90.00
Creation Time : Mon Jun 23 22:51:43 2003
Raid Level : raid0
Array Size : 44457600 (42.40 GiB 45.57 GB)
Raid Devices : 5
Total Devices : 5
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Mon Jun 23 22:51:43 2003
State : dirty, no-errors
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0
Chunk Size : 64K
Number Major Minor RaidDevice State
0 8 48 0 active sync /dev/sdd
1 8 64 1 active sync /dev/sde
2 8 80 2 active sync /dev/sdf
3 8 96 3 active sync /dev/sdg
4 8 112 4 active sync /dev/sdh
UUID : ffa7efb1:1c151f2d:4f6a138c:77085f29
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/