From: Oleg Drokin <green@namesys.com>
To: Derek Fountain <derekfountain@lycos.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: LVM, NFS, Reiser and ext3
Date: Mon, 6 Jan 2003 13:21:29 +0300 [thread overview]
Message-ID: <20030106132129.A2254@namesys.com> (raw)
In-Reply-To: <200301060947.53043.derekfountain@lycos.co.uk>
Hello!
On Mon, Jan 06, 2003 at 09:47:53AM +0000, Derek Fountain wrote:
> correctly written NFS transfers later, I'm seeing errors on read like:
> Jan 6 16:26:47 beetle kernel: EXT3-fs error (device lvm(58,0)): ext3_readdir:
> bad entry in directory #229383: rec_len is too small for name_len -
> offset=504, inode=229395, rec_len=36, name_len=36
> and lots and lots of:
> Jan 6 16:29:34 beetle kernel: attempt to access beyond end of device
> Jan 6 16:29:34 beetle kernel: 3a:00: rw=0, want=629932036, limit=5242880
> Is there reason to believe that LVM, NFS and jouralling file systems don't get
> along?
No.
Looks like there is something with your hardware.
Does corruption go away if you use physical volumes without LVM (try each volume
of three)?
Bye,
Oleg
next prev parent reply other threads:[~2003-01-06 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 9:47 LVM, NFS, Reiser and ext3 Derek Fountain
2003-01-06 10:21 ` Oleg Drokin [this message]
2003-01-07 8:59 ` Derek Fountain
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=20030106132129.A2254@namesys.com \
--to=green@namesys.com \
--cc=derekfountain@lycos.co.uk \
--cc=linux-kernel@vger.kernel.org \
/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