From: Andreas Dilger <adilger@turbolabs.com>
To: Uros Watzak <uros@thz.net>
Cc: linux-lvm@sistina.com
Subject: Re: [linux-lvm] fsck write test
Date: Fri Jan 11 13:29:02 2002 [thread overview]
Message-ID: <20020111122818.V26688@lynx.adilger.int> (raw)
In-Reply-To: <001f01c19ad4$392d5120$803cfad5@vector>; from uros@thz.net on Fri, Jan 11, 2002 at 08:14:35PM +0100
On Jan 11, 2002 20:14 +0100, Uros Watzak wrote:
> Hello Wolfgang.
>
> I have found your e-mail address in an older post on WWW
> in some Linux web board/forum.
This is actually a mailing list address...
> You mentioned there is a
> way to perform a write test on a partirion using fsck or
> mke2fs. Can you tell me how to do it ? I used fsck but it
> only does a read-only test. Is there any way I can do a
> write test on my drive ?
man badblocks(8), see -w and -n parameters. You can optionally
use "mke2fs -c <dev>" to do the badblocks checking at the same
time as you create the filesystem.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
prev parent reply other threads:[~2002-01-11 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 13:15 [linux-lvm] fsck write test Uros Watzak
2002-01-11 13:29 ` Andreas Dilger [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=20020111122818.V26688@lynx.adilger.int \
--to=adilger@turbolabs.com \
--cc=linux-lvm@sistina.com \
--cc=uros@thz.net \
/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