From: Matthew Gillen <me@mattgillen.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Need to keep running fsck on LVM
Date: Fri, 02 Dec 2005 14:32:35 -0500 [thread overview]
Message-ID: <4390A153.90407@mattgillen.net> (raw)
In-Reply-To: <200512020907.52315.t-rigby@shaw.ca>
Terry Rigby wrote:
> Once a week or so I am getting an issue with my volume where I can no longer
> write to it and I get "read only filesystem" errors. I need to unmount it
> and run an fsck.ext3 on it and it will fix errors and then will be fine for
> awhile. I assume that there is a drive that is dying in the array. Is there
> any way or telling which drive this might be?
Have you tried to use smartctl to access SMART data on the drives?
--Matt
next prev parent reply other threads:[~2005-12-02 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 17:07 [linux-lvm] Need to keep running fsck on LVM Terry Rigby
2005-12-02 17:12 ` Erik Ohrnberger
2005-12-02 17:24 ` Terry Rigby
2005-12-02 17:28 ` Erik Ohrnberger
2005-12-02 19:32 ` Matthew Gillen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-02 21:47 Brian Wong
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=4390A153.90407@mattgillen.net \
--to=me@mattgillen.net \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).