xfs
[Top] [All Lists]

Re: rsync and corrupt inodes (was xfs_dump problem)

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: rsync and corrupt inodes (was xfs_dump problem)
From: Linda Walsh <xfs@xxxxxxxxx>
Date: Wed, 07 Jul 2010 14:56:20 -0700
Cc: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
In-reply-to: <20100630233029.GO24712@dastard>
References: <4C26A51F.8020909@xxxxxxxxx> <20100628022744.GX6590@dastard> <4C2A749E.4060006@xxxxxxxxx> <201006302025.20289@xxxxxx> <20100630233029.GO24712@dastard>
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.8.1.24) Gecko/20100228 Lightning/0.9 Thunderbird/2.0.0.24 Mnenhy/0.7.6.666
Dave Chinner wrote:
On Wed, Jun 30, 2010 at 08:25:20PM +0200, Michael Monnerie wrote:
From another Linux ("saturn"), I do an rsync via an rsync-module,
...
Are you running rsync locally on saturn
----

Data point:

I have two file systems with corruption -- one recent one had a WinXP
client (as well as a Win7, and linux host), dumping foreign names into
the file system (the Win clients through samba).

However, my "home partition" use to regularly be used to backup the
WinXP's home dir via  **rsync**.


Some of those files were _un_readable on WinXP (like ones containing copyright
symbols / registered trademark symbols, etc) -- but at the time, they
WERE readable on linux.  Now some of those same files are no longer
readable on linux.  Just thought I'd mention that on my 'home' partition,
the corruption is in files that were transfered with rsync.

<Prev in Thread] Current Thread [Next in Thread>