All these three possibilities will work, but probably (and depending on the number of disks involved) the disk duplicator will be the one least costly, because it can work automatically.
You can verify a medium (any medium, including your MODs) by simply reading from it. Put the newly copied MOD in a drive, and use something similar to this script:
Code:
#! /bin/ksh
mount /dev/<whatever the devicename of the MOD is> /tmp/disktest
if [ $(tar -cvf - /tmp/disktest >/dev/null 2>&1 ; print - $?) -gt 0 ] ; then
print - "ERROR: Disk has read errors"
else
print - "Disk passed read test"
fi
umount /tmp/disktest
exit 0
Quote:
Originally Posted by drew_holm
[...] and have limited IRIX skills
May i ask then, why you post in the experts forum? It surely can't be because of the nature of your problem, which is entry-level at best, yes?
I hope this helps.
bakunin
---------- Post updated 04-19-10 at 11:49 AM ---------- Previous update was 04-18-10 at 06:53 PM ----------
After doing some searching i found no such thing as a media duplicator for MO-media, so perhaps such a thing isn't being produced.
You could build such a device (at least half-automated, that is) yourself by installing two MO-drives in one system. It doesn't even have to be a SGI-workstation, a simple Linux workstation would suffice, which would probably lower the price tremenduously.
Then start the following script (or some variant of it) as root. I have:
Code:
#! /bin/ksh
typeset chInDev="/dev/sdb1" # these are assumptions, probably have to be changed
typeset chOutDev="/dev/sdc1"
typeset fInPath="/tmp/DiskIn"
typeset fOutPath="/tmp/DiskOut"
mkdir -p "$fInPath"
mkdir -p "$fOutPath"
while : ; do
print - "-- Load both drives, then press ENTER --" ; read junk
sleep 20 # give the drives time to spin up, maybe required, maybe not
mount "$chInDev" "$fInPath"
mount "$chOutDev" "$fOutPath"
cd "$fInPath"
tar -cf - * | (cd "$fOutPath" ; tar -xf - )
if [ $? -gt 0 ] ; then
print - "ERROR: could not copy disk!"
else
print - "Disk successfully duplicated."
fi
cd -
umount "$fInPath"
umount "$fOutPath"
done
exit 0
You can stop this script by pressing "CTRL-C", otherwise it will loop forever, asking for one disk after the other.
I have been tasked with archiving Oracle tables. The data is on raw devices, and possibly will span multiple logical volumes.
Has anyone ever had to do this? How did you accomplish it?
Any references to accomplish this would be greatly appreciated.
Thanks, (2 Replies)
Hi all,
Can anybody help me with how I can connect a usb pendrive or external disk to a Sun Server which runs on Solaris 9? I am able to connect the usb drive to a windows server easily and copy files but am wondering if it is possible to do that with Solaris.
Any help will be appreciated. thanks. (3 Replies)
I am trying to list the name of files on an MOD - I use the command
tar vtf /MOD_DRIVE|more
and I get a nice list of filenames/directories on this particular MOD. When I put in another MOD that contains software options I get the error "directory checksum error". I would like to be able to... (2 Replies)
Hello,
we are running Irix 6.5 on our octane/sgi computers - these computers come with an external Sony MOD drive attached via a scsi cable. We have backed info to 2.3 gig MOD disks over the years and woule like to duplicate the MOD's. I believe there are 3 ways to do this:
add a second... (1 Reply)
Got server that I want to have an 'image' of disk to keep in case of failure. What I want to be able to do is, in the event of disk failure, remove system disk replace with cloned disk (same slot) and reboot.
Trouble is I cant take this server down to single user.
Is dd still a viable... (6 Replies)
Discussion started by: psychocandy
6 Replies
LEARN ABOUT FREEBSD
msdosfs
MSDOSFS(5) BSD File Formats Manual MSDOSFS(5)NAME
msdosfs -- MS-DOS file system
SYNOPSIS
options MSDOSFS
DESCRIPTION
The msdosfs driver will permit the FreeBSD kernel to read and write MS-DOS based file systems.
The most common usage follows:
mount -t msdosfs /dev/ada0sN /mnt
where N is the partition number and /mnt is a mount point. Some users tend to create a /dos directory for msdosfs mount points. This helps
to keep better track of the file system, and make it more easily accessible.
It is possible to define an entry in /etc/fstab that looks similar to:
/dev/ada0sN /dos msdosfs rw 0 0
This will mount an MS-DOS based partition at the /dos mount point during system boot. Using /mnt as a permanent mount point is not advised
as its intention has always been to be a temporary mount point for floppy and ZIP disks. See hier(7) for more information on FreeBSD direc-
tory layout.
SEE ALSO mount(2), unmount(2), mount(8), mount_msdosfs(8), umount(8)AUTHORS
This manual page was written by Tom Rhodes <trhodes@FreeBSD.org>.
BSD October 1, 2013 BSD