More iMac/OS X Pain
Discussion
It seems that there is a bug in the DVD burning facility within Finder that causes the write/burn process to fail if a file of size 0bytes is encountered (an Error -36 is reported - can't read file).
Annoyingly this means that the files already burned to the DVD cannot be accessed ('cos the file structure if fubared) and you have to start all over again after an erase.
Anyone come across a workaround for this problem that will let me burn arbitrary folders to a DVD without having to search them to see if there is a 0 size file somewhere?
Annoyingly this means that the files already burned to the DVD cannot be accessed ('cos the file structure if fubared) and you have to start all over again after an erase.
Anyone come across a workaround for this problem that will let me burn arbitrary folders to a DVD without having to search them to see if there is a 0 size file somewhere?
Cant say i've tried it, so not encountered that. If no one can help here, then i'd bet you get a quick reply on the www.macnn.com forums.
Have you got Toast? Might be worth trying to burn with that.. If not then there are still other burning apps to try, many/most of which are free.
P,
Have you got Toast? Might be worth trying to burn with that.. If not then there are still other burning apps to try, many/most of which are free.
P,
Never seen this happen myself - are you sure you can actually read the file, and it has the correct permissions etc. ?
Sounds like a stupid question, but given that OS X is unix underneath, may be worth checking that the 'zero byte file' is a regular file and not a pipe, device, symlink or other unixy thing that OS X doesn't want to burn to disc (or can't because it points to something you don't have permission to read).
I'm assuming the usual stuff is OK - you're copying off a regular journalled HFS+ volume, etc. I've got an NFS mount in my home directory pointing at a different machine that holds my iTunes library, I've found that different OS X utilities treat the NFS mount point differently - some treat it as a zero-byte 'special' file, some ignore it, and some (importantly, ditto) treat it as a hard link and copy the entire contents off the remote machine...
Sounds like a stupid question, but given that OS X is unix underneath, may be worth checking that the 'zero byte file' is a regular file and not a pipe, device, symlink or other unixy thing that OS X doesn't want to burn to disc (or can't because it points to something you don't have permission to read).
I'm assuming the usual stuff is OK - you're copying off a regular journalled HFS+ volume, etc. I've got an NFS mount in my home directory pointing at a different machine that holds my iTunes library, I've found that different OS X utilities treat the NFS mount point differently - some treat it as a zero-byte 'special' file, some ignore it, and some (importantly, ditto) treat it as a hard link and copy the entire contents off the remote machine...
cyberface said:
Never seen this happen myself - are you sure you can actually read the file, and it has the correct permissions etc. ?
Sounds like a stupid question, but given that OS X is unix underneath, may be worth checking that the 'zero byte file' is a regular file and not a pipe, device, symlink or other unixy thing that OS X doesn't want to burn to disc (or can't because it points to something you don't have permission to read).
I'm assuming the usual stuff is OK - you're copying off a regular journalled HFS+ volume, etc. I've got an NFS mount in my home directory pointing at a different machine that holds my iTunes library, I've found that different OS X utilities treat the NFS mount point differently - some treat it as a zero-byte 'special' file, some ignore it, and some (importantly, ditto) treat it as a hard link and copy the entire contents off the remote machine...
The data is actually on a NAS and was originally created by a Windows XP machine. The zero byte files are regular files (albeit very empty), and OS X has no problems with permissions with all other files on the same storage.Sounds like a stupid question, but given that OS X is unix underneath, may be worth checking that the 'zero byte file' is a regular file and not a pipe, device, symlink or other unixy thing that OS X doesn't want to burn to disc (or can't because it points to something you don't have permission to read).
I'm assuming the usual stuff is OK - you're copying off a regular journalled HFS+ volume, etc. I've got an NFS mount in my home directory pointing at a different machine that holds my iTunes library, I've found that different OS X utilities treat the NFS mount point differently - some treat it as a zero-byte 'special' file, some ignore it, and some (importantly, ditto) treat it as a hard link and copy the entire contents off the remote machine...
jeremyc said:
cyberface said:
Never seen this happen myself - are you sure you can actually read the file, and it has the correct permissions etc. ?
Sounds like a stupid question, but given that OS X is unix underneath, may be worth checking that the 'zero byte file' is a regular file and not a pipe, device, symlink or other unixy thing that OS X doesn't want to burn to disc (or can't because it points to something you don't have permission to read).
I'm assuming the usual stuff is OK - you're copying off a regular journalled HFS+ volume, etc. I've got an NFS mount in my home directory pointing at a different machine that holds my iTunes library, I've found that different OS X utilities treat the NFS mount point differently - some treat it as a zero-byte 'special' file, some ignore it, and some (importantly, ditto) treat it as a hard link and copy the entire contents off the remote machine...
The data is actually on a NAS and was originally created by a Windows XP machine. The zero byte files are regular files (albeit very empty), and OS X has no problems with permissions with all other files on the same storage.Sounds like a stupid question, but given that OS X is unix underneath, may be worth checking that the 'zero byte file' is a regular file and not a pipe, device, symlink or other unixy thing that OS X doesn't want to burn to disc (or can't because it points to something you don't have permission to read).
I'm assuming the usual stuff is OK - you're copying off a regular journalled HFS+ volume, etc. I've got an NFS mount in my home directory pointing at a different machine that holds my iTunes library, I've found that different OS X utilities treat the NFS mount point differently - some treat it as a zero-byte 'special' file, some ignore it, and some (importantly, ditto) treat it as a hard link and copy the entire contents off the remote machine...
I've found that tools like subversion won't check out source code successfully to NAS-mounts, but is absolutely fine to local HFS+ volumes.
Just to make sure, you could ditto the entire directory tree to a local Mac HFS+ disk, then try to burn the worm. If that works, it's yet another small, irritating and tricky to track down bug in OS X netcode. If you're accessing the NAS using SMB then I'll bet you a pint of beer that this is the problem. FWIW I've found NFS much more reliable (as in rock-solid) sharing drives between machines, whereas using 'windows sharing' i.e. Samba on OS X as a server and another OS X box using a Samba client to access the share is flaky, unreliable and exhibits odd bugs sometimes...
jeremyc said:
Thanks for the response - not sure I'm sufficiently au fait with my setup to know exactly what I'm doing. 
iMac is standard, out-of-the-box configuration that automagically accessed the NAS that sits on my network. No idea how it accesses it.
In OS X Finder, presumably you use the menu Go / Connect to Server... - if the address in there starts with smb:// then you're accessing a Windows share using Samba. And that's where the problem probably lies...iMac is standard, out-of-the-box configuration that automagically accessed the NAS that sits on my network. No idea how it accesses it.
Get a terminal window up, man ditto, then try using ditto (which copies everything including the Mac legacy metadata with the right command-line switch) to copy the directory off the NAS and onto your Mac (assuming you've got room). If that works, then at least you know where the problem lies
cyberface said:
In OS X Finder, presumably you use the menu Go / Connect to Server... - if the address in there starts with smb:// then you're accessing a Windows share using Samba. And that's where the problem probably lies...
'Get Info' for my NAS shows that the address starts cifs:// and that the format is "Windows Sharing (SMB/CIFS)".Leithen said:
Is your NAS "home made" or an out of the box solution? I'm using an Infrant (Now Netgear) ReadyNas NV+ and there is good forum support for the box - might already have the answer to your probs there?
It is a LaCie and standard out of the box.It looks to me (as suggested below) that some part of OS X is throwing a wobbly when asked to read a zero byte sized file for writing to the DVD.
One day when I've got some time I'll try copying a selection of files to the Mac disk (including some zero sized ones) and trying to burn from there. I seem to remember I've tried this before (and it failed in the same way) but I can't be sure.
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff