>From: [EMAIL PROTECTED] (Bill Davidsen)

>> >Hello
>> >    I was trying to make an image of a specific directory on a vfat
>> >partition but mkisofs refuses to do so.  What did I miss here?
>> >    This is the command I am issuing:
>> 
>> >mkisofs -o image1.raw -D -R -J /mnt/DOS_hda1/Program\ 
>Files/Netscape/Users/mendes/Mail/
>> >Using SUPPO000.SNM;1 for  /Support Creative.snm (Support Caldera.snm)
>> >Using SUPPO000.;1 for  /Support Creative (Support Caldera)
>> >Using SENT_000.;1 for  /Sent_old1 (Sent_old)
>> >Using SENT_000.SNM;1 for  /Sent_old1.snm (Sent_old.snm)
>> >mkisofs: No such file or directory. cannot read from /mnt/DOS_hda1/Program 
>Files/Netscape/Users/mendes/Mail/aic7xxx
>>                                    ^ ^^^^^^^^^^^
>> 
>> The file is already open, so this is a bug in the OS.

>  Or he was backing up a live system and mail came in (or was read or
>whatever). Having a file locked or truncated while backing it up makes
>it unreadable. Doing backups on a live system is a bug in the user.

A OS that works as expected does not remove files that are open.
For this reason, it is impossible that the error code 
"No such file or directory." is retrurned when a read request has been issued.

>  A good backup program will check the modified time after copy, give a
>clear text message on errors, and if the destination is a file it will

Mkisofs gives a clear error message in this case (as you see).
Note that there is only a very short time between opening the file 
and reading it.

>keep a pointer to the start of the destination copy and recopy until a
>clean copy is made or an clear "file is changing" error is reported to
>the user.

The time is not really significant. The only problem that might arise
for a backup program is that the file gets truncated. In this case the backup
program is not able to get the expected amount of data.

>  That's not a criticism of mkisofs, it's not (primarily) designed as a
>backup program, but the error message makes me think that the file was
>moved or deleted on the fly. If this was a local mount it is unlikely
>this happened, but if it was an SMB mount of a remote directory it could
>happen.

>  What is the nature of the mounted filesystem?

THe filesystem code (if correct) may never remove the open file handle in
a way that it does not work anymore for readin in such a situation.

J�rg

 EMail:[EMAIL PROTECTED] (home) J�rg Schilling D-13353 Berlin
       [EMAIL PROTECTED]               (uni)  If you don't have iso-8859-1
       [EMAIL PROTECTED]           (work) chars I am J"org Schilling
 URL:  http://www.fokus.gmd.de/usr/schilling   ftp://ftp.fokus.gmd.de/pub/unix


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

Reply via email to