Re: Multi Volume CD/DVDs

2004-03-19 Thread Andy Polyakov
 Pardon my ignorance, but I would like to ask what is the commonly
 practiced method of creating multi-volume disks.

You must be referring to Volume Sequence Number defined for ISO9660
data-set. I myself would first wonder how common is support for
*accessing* of such multi-volume data-sets. Note that I'm not saying
that I know answer to either question, but I won't be surprised if
support for multi-volume *access* turns to be commonly poor.

 That is, for instance
 I need to burn a directory that has files whose combined size is, say
 12 GB. How would one go about creating multiple ISO9660 images from it
 and then burning them on CD/DVDs. Is there a way that these images can
 themselves keep track of information like their position in the
 sequence, total number of images that constitute the complete dataset
 etc.

Once again you probably should first wonder if and how target OS can use
this multi-volume field, because if it doesn't treat it in the way you
expect it to, then figuring out how to create multi-volume data-set
won't solve the problem.

 Also, what if the things are complicated by the existence of one or
 more files of size  2GB. Is this a Linux only issue?

Note that it's not an inherent Linux limitation, but Linux isofs
implmentation issue. I mean you can access files larger than 2GB under
Linux, but not those residing on ISO9660 volume. And the fact that Linux
exhibits this deficiency doesn't mean that *all* other implementations
are bug-free. I mean breaking 2GB limit is indeed a problem with Linux
isofs implementation, but given this fact alone one can't tell that it's
not a problem on some other given OS.
 
 Is this an issue on 64 bit SGI IRIX systems?

I don't think anybody would be able to answer this question definitely.
The only way is to try... Keep in mind that in Linux it's rather signed
vs. unsigned than 32- vs. 64-bit issue. A.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Multi Volume CD/DVDs

2004-03-19 Thread scdbackup

 ... I would like to ask what is the commonly
 practiced method of creating multi-volume disks. That is, for instance
 I need to burn a directory that has files whose combined size is, say
 12 GB. How would one go about creating multiple ISO9660 images from it
 and then burning them on CD/DVDs.

A few years ago i was faced with the same problem and my solution
is available as open source software :
  http://scdbackup.webframe.org/scdbackup-0.8.tar.gz
see file  README
Homepage :
  http://scdbackup.webframe.org/main_eng.html


In respect to other comments i have read so far :

scdbackup does not use exotic ISO 9660 features. It produces plain
independend ISO filesystems (+RockRidge) on several CDs.

To Andy :

Hi,
scdbackup is one of the off-list answers sent to Norbert Preining
about his request for a 'good' backup program.
I was reluctant to advertise my stuff as such a thing.

Ashish Rangole on the other hand asked for a central feature of scdbackup
which i am proud to present. 
Worthless, of course, without mkisofs, afio, cdrecord or growisofs.
(Taking a bow)

 
 Is there a way that these images can themselves keep track of
 information like their position in the
 sequence, total number of images that constitute the complete dataset
 etc.

scdbackup-0.8 maintains a list of checksum records (MD5) which
may be used to identify a volume of a multi volume backup. Those records
tell date, total number of volumes and sequence number of the given volume.
But this needs to read the whole media and will fail if the media is damaged.
(It's actually intended for verifying write success.)
So you will be better off with a leaflet of paper which holds the desired
information in human readable form. Paint unique, permanent ID numbers on
your media and refer to them on the leaflet. (Staedler Lumocolor pens seem
to do no harm to the surface of a CD-RW. I never tested Edding pens.)

 
 Also, what if the things are complicated by the existence of one or 
 more files of size  2GB. 

That depends wether the affected programs got compiled with 
Large File Support. I was told that mkisofs of cdrtools-2.01a19 
has that feature (there are newer releases meanwhile).


 Is this a Linux only issue? 

Traditional functions and data structures of the file system interface
used 32-bit signed integers (e.g. fseek got parameter  long offset ).
With Linux (and others) there are compile time macros which switch
to more modern data types : _FILE_OFFSET_BITS=64 _LARGEFILE_SOURCE


 Is this an issue on 64 bit SGI IRIX systems?

I suppose that SGI's own programs do support large files while possibly
some third-party programs don't.


scdbackup's programs get compiled with Large File Support. You will
also need mkisofs with that feature (see above).
Nevertheless, when creating ISO 9660 filesystems, scdbackup can not
handle files which are larger than a single media. Therefore files 2GB
can only be backuped on DVD (scdbackup uses growisofs to write the media)
or in format afio (large file support since afio-2.4.7.9beta4).


Have a nice day :)

Thomas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Multi Volume CD/DVDs

2004-03-19 Thread Andy Polyakov
 To Andy :
 
 scdbackup is one of the off-list answers sent to Norbert Preining
 about his request for a 'good' backup program.

Please note that I'm not blaming [nor in position to blame] anybody for
choices they make. I merely *encoraged* public to open up, as it felt
there is a need for that. My comment was *not* based solely on that
particular remark, so don't take it personally.

 I was reluctant to advertise my stuff as such a thing.

Modesty is of course valuable quality, but keep in mind that it's a
*discussion* forum. Statement or proposed solution doesn't have to be
100% correct or perfectly suitable for some particular situation. That's
why we *discuss* it, don't we?

 scdbackup-0.8 maintains a list of checksum records (MD5) which
 may be used to identify a volume of a multi volume backup.

Great!

  Also, what if the things are complicated by the existence of one or
  more files of size  2GB.
 
 That depends wether the affected programs got compiled with
 Large File Support. I was told that mkisofs of cdrtools-2.01a19
 has that feature (there are newer releases meanwhile).
 
  Is this a Linux only issue?
 
 Traditional functions and data structures of the file system interface
 used 32-bit signed integers (e.g. fseek got parameter  long offset ).

Once again. Keep in mind that Linux isofs implementation is deficient in
such way which effectively limits maximum file size to 2G-1 byte. I mean
even if kernel itself supports large files and all application programs
are explicitly compiled with large file support, you still get into
trouble [as long as we're talking about ISO9660 that is]. I assumed that
Ashish was referring to this limitation, as it was discussed serveral
times on this list. I might be wrong in my assumption (but that's OK as
already established:-). Cheers. A.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Multi Volume CD/DVDs

2004-03-19 Thread scdbackup

  On Fri, 19 Mar 2004 [EMAIL PROTECTED] wrote:
 On Fri, 19 Mar 2004, Andy Polyakov wrote:

 My comment was *not* based solely on that
 particular remark, so don't take it personally.

No offense taken.
And if ever ... your merits would outweight it.


  scdbackup-0.8 maintains a list of checksum records (MD5) which
  may be used to identify a volume of a multi volume backup.
 Great!

... and it got a bash script on each CD/DVD which tells you
the volume number, the date and can tell you on which volume a file
may be found. (Silly me, that would have been the better answer.)  


 Once again. Keep in mind that Linux isofs implementation is deficient in
 such way which effectively limits maximum file size to 2G-1 byte.

I was not aware of that. Still using CD-RW and only getting reports
from my DVD users. At least one of them got happy with large files
after pointing me to the lack of Large File Support in scdbackup-0.7 .

Conclusion so far :

For files larger than 2 GB i can only propose to use afio format
rather than ISO. Again: get at least afio-2.4.7.9beta4 for that
and make thorough tests including real restore experiments.
Be aware that 4 GB might be another limit.


Have a nice day :)

Thomas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Multi Volume CD/DVDs

2004-03-19 Thread scdbackup

 ... I would like to ask what is the commonly
 practiced method of creating multi-volume disks. That is, for instance
 I need to burn a directory that has files whose combined size is, say
 12 GB. How would one go about creating multiple ISO9660 images from it
 and then burning them on CD/DVDs.

A few years ago i was faced with the same problem and my solution
is available as open source software :
  http://scdbackup.webframe.org/scdbackup-0.8.tar.gz
see file  README
Homepage :
  http://scdbackup.webframe.org/main_eng.html


In respect to other comments i have read so far :

scdbackup does not use exotic ISO 9660 features. It produces plain
independend ISO filesystems (+RockRidge) on several CDs.

To Andy :

Hi,
scdbackup is one of the off-list answers sent to Norbert Preining
about his request for a 'good' backup program.
I was reluctant to advertise my stuff as such a thing.

Ashish Rangole on the other hand asked for a central feature of scdbackup
which i am proud to present. 
Worthless, of course, without mkisofs, afio, cdrecord or growisofs.
(Taking a bow)

 
 Is there a way that these images can themselves keep track of
 information like their position in the
 sequence, total number of images that constitute the complete dataset
 etc.

scdbackup-0.8 maintains a list of checksum records (MD5) which
may be used to identify a volume of a multi volume backup. Those records
tell date, total number of volumes and sequence number of the given volume.
But this needs to read the whole media and will fail if the media is damaged.
(It's actually intended for verifying write success.)
So you will be better off with a leaflet of paper which holds the desired
information in human readable form. Paint unique, permanent ID numbers on
your media and refer to them on the leaflet. (Staedler Lumocolor pens seem
to do no harm to the surface of a CD-RW. I never tested Edding pens.)

 
 Also, what if the things are complicated by the existence of one or 
 more files of size  2GB. 

That depends wether the affected programs got compiled with 
Large File Support. I was told that mkisofs of cdrtools-2.01a19 
has that feature (there are newer releases meanwhile).


 Is this a Linux only issue? 

Traditional functions and data structures of the file system interface
used 32-bit signed integers (e.g. fseek got parameter  long offset ).
With Linux (and others) there are compile time macros which switch
to more modern data types : _FILE_OFFSET_BITS=64 _LARGEFILE_SOURCE


 Is this an issue on 64 bit SGI IRIX systems?

I suppose that SGI's own programs do support large files while possibly
some third-party programs don't.


scdbackup's programs get compiled with Large File Support. You will
also need mkisofs with that feature (see above).
Nevertheless, when creating ISO 9660 filesystems, scdbackup can not
handle files which are larger than a single media. Therefore files 2GB
can only be backuped on DVD (scdbackup uses growisofs to write the media)
or in format afio (large file support since afio-2.4.7.9beta4).


Have a nice day :)

Thomas



Re: Multi Volume CD/DVDs

2004-03-19 Thread Andy Polyakov
 To Andy :
 
 scdbackup is one of the off-list answers sent to Norbert Preining
 about his request for a 'good' backup program.

Please note that I'm not blaming [nor in position to blame] anybody for
choices they make. I merely *encoraged* public to open up, as it felt
there is a need for that. My comment was *not* based solely on that
particular remark, so don't take it personally.

 I was reluctant to advertise my stuff as such a thing.

Modesty is of course valuable quality, but keep in mind that it's a
*discussion* forum. Statement or proposed solution doesn't have to be
100% correct or perfectly suitable for some particular situation. That's
why we *discuss* it, don't we?

 scdbackup-0.8 maintains a list of checksum records (MD5) which
 may be used to identify a volume of a multi volume backup.

Great!

  Also, what if the things are complicated by the existence of one or
  more files of size  2GB.
 
 That depends wether the affected programs got compiled with
 Large File Support. I was told that mkisofs of cdrtools-2.01a19
 has that feature (there are newer releases meanwhile).
 
  Is this a Linux only issue?
 
 Traditional functions and data structures of the file system interface
 used 32-bit signed integers (e.g. fseek got parameter  long offset ).

Once again. Keep in mind that Linux isofs implementation is deficient in
such way which effectively limits maximum file size to 2G-1 byte. I mean
even if kernel itself supports large files and all application programs
are explicitly compiled with large file support, you still get into
trouble [as long as we're talking about ISO9660 that is]. I assumed that
Ashish was referring to this limitation, as it was discussed serveral
times on this list. I might be wrong in my assumption (but that's OK as
already established:-). Cheers. A.



Re: Multi Volume CD/DVDs

2004-03-19 Thread scdbackup

  On Fri, 19 Mar 2004 [EMAIL PROTECTED] wrote:
 On Fri, 19 Mar 2004, Andy Polyakov wrote:

 My comment was *not* based solely on that
 particular remark, so don't take it personally.

No offense taken.
And if ever ... your merits would outweight it.


  scdbackup-0.8 maintains a list of checksum records (MD5) which
  may be used to identify a volume of a multi volume backup.
 Great!

... and it got a bash script on each CD/DVD which tells you
the volume number, the date and can tell you on which volume a file
may be found. (Silly me, that would have been the better answer.)  


 Once again. Keep in mind that Linux isofs implementation is deficient in
 such way which effectively limits maximum file size to 2G-1 byte.

I was not aware of that. Still using CD-RW and only getting reports
from my DVD users. At least one of them got happy with large files
after pointing me to the lack of Large File Support in scdbackup-0.7 .

Conclusion so far :

For files larger than 2 GB i can only propose to use afio format
rather than ISO. Again: get at least afio-2.4.7.9beta4 for that
and make thorough tests including real restore experiments.
Be aware that 4 GB might be another limit.


Have a nice day :)

Thomas



Multi Volume CD/DVDs

2004-03-18 Thread Ashish Rangole
Pardon my ignorance, but I would like to ask what is the commonly
practiced method of creating multi-volume disks. That is, for instance
I need to burn a directory that has files whose combined size is, say
12 GB. How would one go about creating multiple ISO9660 images from it
and then burning them on CD/DVDs. Is there a way that these images can 
themselves keep track of information like their position in the
sequence, total number of images that constitute the complete dataset
etc.

Also, what if the things are complicated by the existence of one or 
more files of size  2GB. Is this a Linux only issue? Is this an issue
on 64 bit SGI IRIX systems?

I did read mkisofs man page but could not understand how exactly
to get this done. Please advise. I shall really appreciate any response.

Thanks in advance for your time and help.

Ashish


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Multi Volume CD/DVDs

2004-03-18 Thread Ashish Rangole
Pardon my ignorance, but I would like to ask what is the commonly
practiced method of creating multi-volume disks. That is, for instance
I need to burn a directory that has files whose combined size is, say
12 GB. How would one go about creating multiple ISO9660 images from it
and then burning them on CD/DVDs. Is there a way that these images can 
themselves keep track of information like their position in the
sequence, total number of images that constitute the complete dataset
etc.

Also, what if the things are complicated by the existence of one or 
more files of size  2GB. Is this a Linux only issue? Is this an issue
on 64 bit SGI IRIX systems?

I did read mkisofs man page but could not understand how exactly
to get this done. Please advise. I shall really appreciate any response.

Thanks in advance for your time and help.

Ashish