OK, I'm pretty certain this is actually an issue with my hard drive, but
I just want to check to make absolutely certain that nothing Wine does
could cause this problem.
I have just set about getting a regular backup of my PC (yes, I know,
consider my wrists to be well and truly slapped for taking nearly two
years to get around to this) and am trying to use rsync to copy files to
a Western Digital Passport USB HDD. However, when I try the following
command
rsync -a /home/david/ /media/Portable/backup/
it chokes when it gets to the .wine folder - I/O error on every single
file and folder within .wine - trying a simple
cp -r /home/david/ /media/Portable/backup/
has the same effect. This is repeatable and only .wine is affected -
which is why I wonder if it could be something about the way Wine is set
up. Could *anything* wine does *possibly* cause this?
Many thanks, in advance,
David Shaw
rsyncing Wine fails
-
Dan Kegel
rsyncing Wine fails
On Mon, Apr 28, 2008 at 3:33 PM, David Shaw <[email protected]> wrote:
What filesystem is your backup volume?
Does it allow filenames that start with . ?
i.e. does
touch /media/Portable/backup/.foobar
succeed?
Not terribly likely...it chokes when it gets to the .wine folder - I/O error on every single file
and folder within .wine - trying a simple
cp -r /home/david/ /media/Portable/backup/
has the same effect. This is repeatable and only .wine is affected - which
is why I wonder if it could be something about the way Wine is set up.
What filesystem is your backup volume?
Does it allow filenames that start with . ?
i.e. does
touch /media/Portable/backup/.foobar
succeed?
-
David Shaw
rsyncing Wine fails
Dan Kegel wrote:
really expect it to be Wine's fault - it's just the fact that it's only
happening when rsync gets to .wine that planted the seeds of doubt - I
just wanted to make certain before I started poking into my filesystems.
Many thanks,
David
//
It's formatted to ext3 and does support .file filenames. I didn'tOn Mon, Apr 28, 2008 at 3:33 PM, David Shaw <[email protected]> wrote:
Not terribly likely...it chokes when it gets to the .wine folder - I/O error on every single file
and folder within .wine - trying a simple
cp -r /home/david/ /media/Portable/backup/
has the same effect. This is repeatable and only .wine is affected - which
is why I wonder if it could be something about the way Wine is set up.
What filesystem is your backup volume?
Does it allow filenames that start with . ?
i.e. does
touch /media/Portable/backup/.foobar
succeed?
really expect it to be Wine's fault - it's just the fact that it's only
happening when rsync gets to .wine that planted the seeds of doubt - I
just wanted to make certain before I started poking into my filesystems.
Many thanks,
David
//
-
Roy Butler
rsyncing Wine fails
David Shaw wrote:
variables. Curious - does wine still work for you w/o issue on this system?
Roy
Testing "cp -r /home/david/.wine/ /var/tmp" would eliminate a lot of theDan Kegel wrote:It's formatted to ext3 and does support .file filenames. I didn'tOn Mon, Apr 28, 2008 at 3:33 PM, David Shaw <[email protected]>
wrote:
Not terribly likely...it chokes when it gets to the .wine folder - I/O error on every
single file
and folder within .wine - trying a simple
cp -r /home/david/ /media/Portable/backup/
has the same effect. This is repeatable and only .wine is affected
- which
is why I wonder if it could be something about the way Wine is set up.
What filesystem is your backup volume?
Does it allow filenames that start with . ?
i.e. does
touch /media/Portable/backup/.foobar
succeed?
really expect it to be Wine's fault - it's just the fact that it's only
happening when rsync gets to .wine that planted the seeds of doubt - I
just wanted to make certain before I started poking into my filesystems.
Many thanks,
David
//
variables. Curious - does wine still work for you w/o issue on this system?
Roy
-
Alan Lord
rsyncing Wine fails
Roy Butler wrote:
<snip />
directory to another server. I'm on Ubuntu 7.10.
The problem I discovered was that in the .wine directory were some
symbolic links to other partitions on my machine and they had rather
unusual names for linux like $d:: or some such and pointed to hard disk
partitions my DVD-RW *and* my DVD-RAM drive.
Anyway, I ended up tar'ing the .wine directory first, then deleting the
actual directory. Extracting the .wine tarball checked out fine afterwards.
<ducks from flames>It was the same for my .ies4linux directory
too!</ducks from flames>
Perhaps it is something like this?
HTH
Al
--
The way out is open!
http://www.theopensourcerer.com
<snip />
I had a major PITA yesterday when trying to backup (by copying) by homeTesting "cp -r /home/david/.wine/ /var/tmp" would eliminate a lot of the
variables. Curious - does wine still work for you w/o issue on this
system?
directory to another server. I'm on Ubuntu 7.10.
The problem I discovered was that in the .wine directory were some
symbolic links to other partitions on my machine and they had rather
unusual names for linux like $d:: or some such and pointed to hard disk
partitions my DVD-RW *and* my DVD-RAM drive.
Anyway, I ended up tar'ing the .wine directory first, then deleting the
actual directory. Extracting the .wine tarball checked out fine afterwards.
<ducks from flames>It was the same for my .ies4linux directory
too!</ducks from flames>
Perhaps it is something like this?
HTH
Al
--
The way out is open!
http://www.theopensourcerer.com
