RE: Newbie: -tsize vs -j

This is for a 500 cd/dvd jukebox with 2 drives. The backups are handled by a
tape jukebox. Mtx handles both jukeboxes very well.

I wonder if a loopback file driver against a cd or dvd sized file would
work? If star recognizes the disk out of space as a EOT that should work. -
Tried it below - star (bzip2?) doesn't seem to handle the disk full as an
EOT.


star: star 1.5a57 (i386-pc-solaris2.8)

bash-3.00# mkfile 100m /export/home/test.ufs     (100m as a quick test)
bash-3.00# lofiadm -a /export/home/test.ufs /dev/lofi/1
bash-3.00# newfs /dev/rlofi/1
newfs: construct a new file system /dev/rlofi/1: (y/n)? y
/dev/rlofi/1:   204600 sectors in 341 cylinders of 1 tracks, 600 sectors
        99.9MB in 22 cyl groups (16 c/g, 4.69MB/g, 2240 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
 32, 9632, 19232, 28832, 38432, 48032, 57632, 67232, 76832, 86432,
 115232, 124832, 134432, 144032, 153632, 163232, 172832, 182432, 192032,
201632
bash-3.00# ls /mnt
bash-3.00# mount /dev/lofi/1 /mnt
bash-3.00# ls -la /mnt
total 20
drwxr-xr-x   3 root     root         512 Apr 24 13:44 .
drwxr-xr-x  39 root     root        1024 Apr 24 03:25 ..
drwx------   2 root     root        8192 Apr 24 13:44 lost+found
bash-3.00#
bash-3.00# /opt/csw/bin/star -cj  \
> -multivol -dump -M \
> -C=/usr \
> -acl -artype=exustar f=/mnt/file.tar.gz \
> level=0 -time .
/opt/csw/bin/star: No such file or directory. Warning no /etc/tardumps.
Type of this level 0P dump: partial
Date of this level 0P dump: Mon Apr 24 13:45:46 2006
Date of last level 0  dump: the epoch

/opt/csw/bin/star: Error 0. Sync pipe read error on pid 8878 flags 0x1.


/opt/csw/bin/star: 33272 blocks + 0 bytes (total of 340705280 bytes =
332720.00k).
/opt/csw/bin/star: Total time 128.165sec (2596 kBytes/sec)
bash-3.00# umount /mnt
bash-3.00# lofiadm -d /dev/lofi/1



-----Original Message-----
From: Daniel Davidson [mailto:[email protected]] 
Sent: Monday, April 24, 2006 1:02 PM
To: [email protected]
Cc: [email protected]
Subject: RE: [Star-users] Newbie: -tsize vs -j


Ahh, now I see what the problem is.  I can think of two things that
might work.

One solution would be to make your script very smart, and if a file was
larger than a cd, you could send it a tsize of something small (100MB?)
and just put the chunks of data on the cd as they will fit.  Unless you
are backing up CD or DVD images, I find your problem is not very common,
so this solution would be in my opinion ok for the worst case scenario.

The other solution will probably not work since I have not tried it,
Jorg probably knows best.  You might be able to just write to
the /dev/hdc or whatever device your cd writer is maybe when it gets
full it will send an EOT (end of tape) signal like a tape drive will.
If it works, that would be spiffy.  If it doesn't work, maybe somewhere
there is a driver that will cause a cdr to show up as a tape device.

I highly recommend going to tape.  You can get into an LTO for around
$1000, or internal AIT2 for $500.  That's not much in the grand scheme
of things.  You will end up with less to manage, and in my opinion have
a vastly improved system.  There are cheaper systems out there also, but
I would say these would be a good place to start if you are on a tight
budget.

I use a SAIT autoloader from Quantum for my stuff, and I am not going
back.  With mtx and star, I can start a backup on Friday, and have the
whole thing finished on Monday when I get to work, no attention needed.

Dan

On Mon, 2006-04-24 at 12:02 -0400, [email protected] wrote:
> Hi Dan,
> 
> Thanks for the reply! 
> 
> I couldn't see a solution when the file to be added is larger than the
> desired tsize.  
> 
> 
<snip>