From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Problems with 0.9.1b7 and 2.2.20-2
Date: Mon, 18 Jun 2001 17:39:11 +0200 [thread overview]
Message-ID: <20010618173911.A15676@sistina.com> (raw)
In-Reply-To: <20010605154656.A1384@jaquet.dk>; from rasmus@jaquet.dk on Tue, Jun 05, 2001 at 03:46:57PM +0200
On Tue, Jun 05, 2001 at 03:46:57PM +0200, Rasmus Andersen wrote:
> On Tue, Jun 05, 2001 at 12:34:17PM +0200, Heinz J. Mauelshagen wrote:
> >
> > This sounds like a well known ext2 problem.
> > Did you run fsck successfully? And if so, didn't it work again?
>
> Uhm. Known problem? Could you elaborate a bit?
I was refering to ext2 consistency problems in older kernels which have been
fixed in the meantime. You need to have recent ext2 tool as well.
> I have not seen it
> before and would like to know if it is something I will encounter
> regularily using ext2 and LVM.
No, you shouldn't in case you have recent ext2 software.
>
> I have run e2fsck a number of times now, and while I do not get
> the kernel log message after the reboot (se below) fsck complain
> and fix stuff every time in lost+found which contain a lot of
> junk I cannot delete manually either.
>
> >
> >
> > >
> > > I can do a 'dd if=/dev/<diskX> of=/dev/null' for the disks that are
> > > part of the volume group without problems but if I do it for /dev/vg1/
> > > lvol4, I get the error above (without the EXT2-part).
> >
> > Did you *really* run "dd if=/dev/vg1/lvol4 of=/dev/null" and got that error
> > in the log? Never have seen that before.
>
> I will try to reproduce. But trying to get as much as the (used)
> filesystem with off the disk with tar resulted in a kernel panic
> (this was just after my last mail):
>
> panic: brw_page: page not locked for IO
>
> This was put after a couple of lines of
>
> Jun 5 10:04:35 firewall kernel: attempt to access beyond end of device
> Jun 5 10:04:35 firewall kernel: 08:01: rw=0, want=530420, limit=410608
> Jun 5 10:04:35 firewall kernel: dev 3a:03 blksize=1024 blocknr=622592 sector=1060832 size=4096 count=1
>
> on the console.
>
> --
> Regards,
> Rasmus(rasmus@jaquet.dk)
>
> "I'm not going to have some reporters pawing through our papers. We are
> the president." -Hillary Clinton commenting on the release of subpoenaed
> documents.
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2001-06-18 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-05 7:24 [linux-lvm] Problems with 0.9.1b7 and 2.2.20-2 Rasmus Andersen
2001-06-05 10:34 ` Heinz J. Mauelshagen
2001-06-05 13:46 ` Rasmus Andersen
2001-06-05 14:05 ` Rasmus Andersen
2001-06-05 19:02 ` Rasmus Andersen
2001-06-18 15:40 ` Heinz J. Mauelshagen
2001-06-18 15:39 ` Heinz J. Mauelshagen [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=20010618173911.A15676@sistina.com \
--to=mauelshagen@sistina.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.