On Mon, Feb 21, 2005 at 12:37:53PM +0100, Andreas Steinmetz [EMAIL PROTECTED]
wrote:
Anyway, what do you guys think could be the problem? Could it be that
the LVM / Device Mapper snapshot feature is solely responsible for
this corruption? (I'm sure there's a reason it's marked
On Tue, Feb 22, 2005 at 08:39:21PM +0100, Andreas Steinmetz [EMAIL PROTECTED]
wrote:
To clarify: there were no disk I/O errors, only I/O errors were reported
by find during operation so it is definitely filesystem corruption
that is going on here.
Though find performs heavy read activity
On Tue, Feb 22, 2005 at 02:46:44PM -0600, Alex Adriaanse [EMAIL PROTECTED]
wrote:
On Tue, 22 Feb 2005 20:49:00 +0100, Marc A. Lehmann [EMAIL PROTECTED] wrote:
Well, I do use reiserfs-aes-loop-lvm/dm-md5/raid5, and it never failed
for me, except once, and the error is likely to be outside
On Thu, Jan 27, 2005 at 06:11:34AM +0100, Andi Kleen [EMAIL PROTECTED] wrote:
Marc Lehmann [EMAIL PROTECTED] writes:
The summary seems to be that the linux raid driver only protects your data
as long as all disks are fine and the machine never crashes.
as long as the machine never
On Thu, Jan 27, 2005 at 10:51:02AM +0100, Andi Kleen [EMAIL PROTECTED] wrote:
The nasty part there is that it can affect completely unrelated
data too (on a traditional disk you normally only lose the data
that is currently being written) because of of the relationship
between stripes on
On Mon, Feb 21, 2005 at 12:37:53PM +0100, Andreas Steinmetz <[EMAIL PROTECTED]>
wrote:
> >Anyway, what do you guys think could be the problem? Could it be that
> >the LVM / Device Mapper snapshot feature is solely responsible for
> >this corruption? (I'm sure there's a reason it's marked
>
On Thu, Jan 27, 2005 at 06:11:34AM +0100, Andi Kleen <[EMAIL PROTECTED]> wrote:
> Marc Lehmann <[EMAIL PROTECTED]> writes:
> >
> > The summary seems to be that the linux raid driver only protects your data
> > as long as all disks are fine and the machine never crashes.
>
> "as long as the
On Thu, Jan 27, 2005 at 10:51:02AM +0100, Andi Kleen <[EMAIL PROTECTED]> wrote:
> The nasty part there is that it can affect completely unrelated
> data too (on a traditional disk you normally only lose the data
> that is currently being written) because of of the relationship
> between stripes on
On Tue, Feb 22, 2005 at 08:39:21PM +0100, Andreas Steinmetz <[EMAIL PROTECTED]>
wrote:
> To clarify: there were no disk I/O errors, only I/O errors were reported
> by find during operation so it is definitely filesystem corruption
> that is going on here.
> Though find performs heavy read
On Tue, Feb 22, 2005 at 02:46:44PM -0600, Alex Adriaanse <[EMAIL PROTECTED]>
wrote:
> On Tue, 22 Feb 2005 20:49:00 +0100, Marc A. Lehmann <[EMAIL PROTECTED]> wrote:
> > Well, I do use reiserfs->aes-loop->lvm/dm->md5/raid5, and it never failed
> > for me, except once, and the error is likely to be
10 matches
Mail list logo
