Use dvdisaster to protect backups on optical media
Thu, 07 Feb 2008 09:00:00 GMT
Storing backups on optical media such as DVD-R discs suffers from two major drawbacks: DVD discs are easy to scratch, and the media itself degrades after a while. You can deal with the scratching issue by careful handing of the media, but even expensive media becomes unreadable over time. Dvdisaster aims to help you recover the information off scratched and aged media.
Hi
My P6 server is with dual vio servers. From the below output we could see that cd devices(cd0 and cd1) has been mapped to the vio client named prdsapfi1.
When we execute "lsdev -Cc cdrom" in prdsapfi1 there are 2 cd devices named cd0 and cd1 showing up in available state.
... (1 Reply)
Running Slackware 13.37 original without updates.
Need to replace my trackball with optical mouse temporarily.
There is no xf86config file anylonger but xorg.conf file is produced automatically.
I see 2 "xorg.conf" files which can be and were modified on installation:
1) /etc/X11/xorg.conf-vesa... (2 Replies)
hello,
someone gave me a set of electronic gadgets 'Brookstone' which has mini optical mouse. This mouse label doesn't have model or etc. Mouse does not work properly i.e. pointer is moving right but left/right buttons work opposite and not always could open or close controls.
I suggest it might... (3 Replies)
We are trying to make duplicates of some Magneto Optical Disks that were created in Irix 6.5. The disks are 2.3 gig and the using a scsi MOD drive. Is there possbily a disk copy like in dos or some simple script to do this - any help appreciated.
Thanks (0 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)
Hi guys,
I have not connected optical cable to the Dual port HBA before. My integrator used to do that for me all the time. Can someone explain to me how can I physically connect optical cable to the HBA port in P570.
The optical cable has two connectors and right now the HBA port has just a... (7 Replies)
Trying to get my unix system to recognize an optical drive, it was delivered to us, so we assumed it worked, in the 2 years since no one ever has used it, we want to now. However, even running probe-scsi-all doesn't bring up that drive. It's a scsi address of 3, at the end of the chain, all... (1 Reply)
Hi,
I tried to install Magneto-Optical (MO) drive Fujutsu to COMPAQ Proliant ML350 with SCO Openserver 5.0.5. Harddisk and MO are connected to Adaptec UW-SCSI-3 (driver ad160).
During boot process system shows me that MO is connected to host adapter 1, bus 0, SCSI ID 1 and LUN 0. But when I... (2 Replies)
MOUNT_UDF(8) BSD System Manager's Manual MOUNT_UDF(8)NAME
mount_udf -- mount a UDF filesystem
SYNOPSIS
mount_udf [-o options] [-s sessionStart] [-n lastRecordedLBA] [-b blockSize] [-p packetSizeInBlocks] [-v verificationPolicy] [-w] devicePath
mountPath
DESCRIPTION
The mount_udf command attaches the UDF filesystem residing on the device devicePath to the global filesystem namespace at the location indi-
cated by mountPath. This command is normally executed by mount(8) at boot time.
The options are as follows:
-o options
Options are specified with a -o flag followed by a comma separated string of options. See the mount(8) man page for possible options
and their meanings.
-v verificationPolicy
This is an advanced option not useful for regular use. It controlls the verification policy when writing to RW type optical media.
Its value can be "meta", "all", or "none". Policy "meta" means only the metadata are verified after they are written. This is the
default policy. Policy "all" means to verify data written, which could be several times slower than policy "meta". Policy "none"
does not verify any data. It is only slightly faster than "meta" in normal cases, but may result a corrupted UDF disc if the write
of metadata fails.
-s sessionStart
This is an advanced option not useful for regular use. When manually mounting a UDF volume with Virtual Partition, it specifies the
start Logical Block Address of the last session where UDF data structures (VRS and AVDP) resides. This value overrides the value
obtained from the device.
-n lastRecordedLBA
This is an advanced option not useful for regular use. When manually mounting a UDF volume with Virtual Partition, it specifies the
last recorded Logical Block Address where the UDF VAT ICB will be searched. This value overrides the value obtained from the device.
-b blockSize
This is an advanced option not useful for regular use. It specifies the block size in bytes used when mounting the UDF volume. This
value overrides the value obtained from the device.
-p packetSizeInBlocks
This is an advanced option not useful for regular use. It specifies the packet size in blocks when manually mounting the UDF volume.
This value overrides the value obtained from the device.
-w This is an advanced option not useful for regular use. It forces to enable the experimental packet writing function on optical media
that has not been fully supported, such as CD-R, CD-RW, DVD-R, DVD+R, HD DVD-R, and BD-R. Writing to these media does not work on
some drives and may cause data corruption or data loss on some other drives. Therefore, this flag should be used only by file system
developers when debugging the experimental write functions.
The -s, -n, -b, and -p flags are not useful in normal use. They are mainly used for debugging and data recovery. Since the -s, -n, and -p
flags are all specified in units of block size, when any of these flags are specified, it is strongly recommended that the -b flag is also
specified.
SEE ALSO mount(2), unmount(2), fstab(5), mount(8)BUGS
Reading of all UDF revisions (1.02 - 2.60) on both block device (e.g., hard drives and USB drives) and most optical media is supported.
Writing to block devices, DVD-RW and DVD+RW is supported with the following exceptions: (1) Cannot write Finder Info, Resource Fork, or other
extended attributes in UDF volumes of revision 1.02 and 1.50; (2) Cannot write to mirrored metadata partition.
HISTORY
The mount_udf utility first appeared in Mac OS X.
4th Berkeley Distribution December 6, 2006 4th Berkeley Distribution