All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm-problems?
Date: Mon, 28 May 2001 11:40:46 +0000	[thread overview]
Message-ID: <20010528114046.K26710@sistina.com> (raw)
In-Reply-To: <20010527234117.A759@mind.bartosch.net>; from peter@bartosch.net on Sun, May 27, 2001 at 11:41:17PM +0200

Did you report that to the reiserfs list too?

On Sun, May 27, 2001 at 11:41:17PM +0200, Peter Bartosch wrote:
> hello,
> 
> i recently made my three LV new (caused by an accident as i tried to
> extend an existing (0.8i) LV)
> 
> so i created a new kernel (2.4.2) with lvm 0.9.1_beta7
> 
> the first problems came when i tried to create more than one VG - the
> second VG couldn't be activated (always inactive after reboot and unable
> to activate)
> 
> so i'm using only one VG
> 
> the first two LV's of this VG could i create without problems, but the
> third makes problems:
> 
> i created the reiserfs on it, but when i tried to mount it, the mount
> failed
> an reiserfsck --rebuild-sb and after that reiserfsck --rebuild-tree
> clears it and i could mount my LV -- UNTIL the next reboot
> 
> i had to reboot because something oopsed:
> 
> ----
> 
> is_leaf: item location seems wrong (second one): *NEW* [9 10 0x0 SD],
> item_len 44, item_location 2308, free_space(entry_count) 65535
> vs-5150: search_by_key: invalid format found in block 8271. Fsck?
> kernel BUG at namei.c:343!
> invalid operand: 0000
> CPU:    0
> EIP:    0010:[<c018ff08>]
> EFLAGS: 00010286
> eax: 0000001b   ebx: c6655e58   ecx: 00000001   edx: 00000001
> esi: c02d4fb4   edi: c6655edc   ebp: c6655e70   esp: c6655e40
> ds: 0018   es: 0018   ss: 0018
> Process cp (pid: 1799, stackpage=c6655000)
> Stack: c02d4c7e c02d4d7e 00000157 00000000 c02d4fb4 c6655e9c 00000002 0000000e 
> 	4a0507ff 000001f4 00000000 00000003 c3e55a20 c0190030 c7742c20 c7dd3b20 
>         0000001b c6655e9c c6655edc fffffff4 c6654000 c7742c20
> 	c3e55a20 00000001 
> Call Trace: [<c0190030>] [<c01468e9>] [<c013de9a>]
>         [<c013e6e9>] [<c013db5a>] [<c013ee4c>] [<c013b8c6>] 
>         [<c0133047>] [<c0108f5b>] 
> Code: 0f 0b 83 c4 0c 8d 76 00 8b 4d 10 51 8b 45 0c 50 57 8d 55 e8 
> 
> -----
> 
> this oops let the process which works on the third LV freeze - so i
> couldn't kill it
> 
> the first and the second LV seem to work well
> 
> when i reboot the third LV won't be mountet automagically and the
> filesystem seems to be corrupt
> 
> 
> any help will be appreciated
> 
> 
> :wq - until next mail B-), l8r
> 
> Peter
> -- 
>    :~~~~~~~~~~~~~~~~~~  peter@bartosch.net  ~~~~~~~~~~~~~~~~~~:
>    :          student of technical computer science           :
>    :     university of applied sciences krefeld (germany)     :
>     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>    FD314F21   C7 AE 2F 28 C1 33 71 77  0D 77 CD 6E 58 E9 06 6B
> _______________________________________________
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2001-05-28 11:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-27 21:41 [linux-lvm] lvm-problems? Peter Bartosch
2001-05-28 11:40 ` Heinz J. Mauelshagen [this message]
2001-05-28 16:32   ` Peter Bartosch

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=20010528114046.K26710@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.