We have a brand new Dell server with an Ultrium 5 tape drive and we're having trouble using the standard
Typically
With the new system, it causes the tape drive to make horrible stopping and starting sounds that ultimately make you wish the server had a face so you could punch it.
I have seen recommendations for -C or -b options, but those seem to be for optimizing performance. I couldn't find any reasonable method of determining whether you have chosen good numbers or not, so I have not been messing with those.
The problem with testing is that each time we try something, the drive will do alternately short high- and low-pitched whines, then sometimes a very long one. It sounds a bit like the tape is winding forwards and backwards, looking for something it can't find. Eventually it hits the end of the tape, rewinds to the beginning, and tries again. I have no evidence of this, it's just what it sounds like.
After a long time of making this racket, and without the usual indicator explaining how much progress is being made, we attempt to kill the processes, and it never works. I've done enough dumping in my day to know that it should be in the process of dumping data normally to tape by this time, so I'm not just being impatient. I've left it for an hour to dump a few hundred M and it never finishes.
Rebooting is then necessary.
At this point it hangs, makes a bunch of noise, and never progresses.
These processes are visible:
The first process can be killed with a
Any suggestions for things to experiment with? Previously, we've gotten new servers that required an extra parameter (or a lack of one we used to use) to make things magically work. Testing is taking more work than usual, since every time we try a new thing, we have to wait a while, then reboot.
We only have to do this about every 5 years, when we get a new server, so we are not
Any help and/or wild speculation would be appreciated. Thanks!
dump
command which has worked fine for us since the beginning of time.Typically
/sbin/dump 0Lauf /dev/nsa0 /dev/<thefilesystem>
has worked fine.With the new system, it causes the tape drive to make horrible stopping and starting sounds that ultimately make you wish the server had a face so you could punch it.
I have seen recommendations for -C or -b options, but those seem to be for optimizing performance. I couldn't find any reasonable method of determining whether you have chosen good numbers or not, so I have not been messing with those.
The problem with testing is that each time we try something, the drive will do alternately short high- and low-pitched whines, then sometimes a very long one. It sounds a bit like the tape is winding forwards and backwards, looking for something it can't find. Eventually it hits the end of the tape, rewinds to the beginning, and tries again. I have no evidence of this, it's just what it sounds like.
After a long time of making this racket, and without the usual indicator explaining how much progress is being made, we attempt to kill the processes, and it never works. I've done enough dumping in my day to know that it should be in the process of dumping data normally to tape by this time, so I'm not just being impatient. I've left it for an hour to dump a few hundred M and it never finishes.
Rebooting is then necessary.
Code:
# /sbin/dump 0Lauf /dev/nsa0 /dev/mfid0p2
DUMP: Date of this level 0 dump: Thu Mar 5 09:40:42 2015
DUMP: Date of last level 0 dump: the epoch
DUMP: Dumping snapshot of /dev/mfid0p2 (/) to /dev/nsa0
DUMP: mapping (Pass I) [regular files]
DUMP: mapping (Pass II) [directories]
DUMP: estimated 964590 tape blocks.
At this point it hangs, makes a bunch of noise, and never progresses.
These processes are visible:
Code:
root 838 0.0 0.0 12440 2136 0 I+ 9:40AM 0:00.00 /sbin/dump 0Lauf /dev/nsa0 /dev/mfid0p2 (dump)
root 840 0.0 0.0 12440 2132 0 D+ 9:40AM 0:00.00 /sbin/dump 0Lauf /dev/nsa0 /dev/mfid0p2 (dump)
The first process can be killed with a
kill -9
, but the second is invincible.Any suggestions for things to experiment with? Previously, we've gotten new servers that required an extra parameter (or a lack of one we used to use) to make things magically work. Testing is taking more work than usual, since every time we try a new thing, we have to wait a while, then reboot.
We only have to do this about every 5 years, when we get a new server, so we are not
dump
experts, except to know that, when it's working, it's very safe and effective.Any help and/or wild speculation would be appreciated. Thanks!