Linux LVM users
 help / color / mirror / Atom feed
From: Kai Weber <lists@glorybox.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Strange file system errors
Date: Fri Jan 16 12:31:01 2004	[thread overview]
Message-ID: <20040116173018.GA32555@glorybox.de> (raw)
In-Reply-To: <1074125783.18105.55.camel@gecko.indygecko.com>

* Jord Tanner <jord@indygecko.com>:

> Try the tests again with write caching off. You can do this with "hdparm
> -W0 /dev/hdX"

Thanks for your help. Until today I can not force the filesystem
corruption with write caching off. Your tip seems to work. The downsize
of disabled write caching seems to be a slightly slower system when
writing large files to the disks.

OK. End Of Topic. and now to something completely different.

-- 
  Kai Weber
» kai.weber@glorybox.de
  http://www.glorybox.de

      reply	other threads:[~2004-01-16 12:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-14  6:36 [linux-lvm] Strange file system errors Kai Weber
2004-01-14 18:22 ` Heinz Mauelshagen
2004-01-14 18:44   ` Kai Weber
2004-01-14 19:17     ` Jord Tanner
2004-01-16 12:31       ` Kai Weber [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040116173018.GA32555@glorybox.de \
    --to=lists@glorybox.de \
    --cc=linux-lvm@sistina.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox