Linux LVM users
 help / color / mirror / Atom feed
From: Peter Bartosch <peter@bartosch.net>
To: reiserfs-list@namesys.com, linux-lvm@sistina.com
Subject: Re: [linux-lvm] Re: [reiserfs-list] lvm-list pointed to reiserfs: fs/lvm-problems?
Date: Thu, 31 May 2001 20:40:03 +0200	[thread overview]
Message-ID: <20010531204003.A806@mind.bartosch.net> (raw)
In-Reply-To: <15124.56124.422024.340431@crimson.namesys.com>; from zam@namesys.com on Wed, May 30, 2001 at 03:36:28PM +0400

Hi!


>  >> 
>  >> Sorry, but it looks for me like a lvm problem.  Can you test you LV by
>  >> coping some random data (~ 64 MB) to a file in reliable location and
>  >> to LV, and compare them (or md5 hashes) after reboot ?
> 
>  PB> hmm, i haven't really tried another filesystem, maybe i should try ext2?
> 
> Yes, try to run this script over ext2:
> http://namesys.com/stress.sh

i've done that, but it gave me some cruel errors - like an ext2 panic or
so (can't find anything about it in the logs)

anyway - the PC was frozen


after the reboot e2fsck showed me that:

Inode 1313467 has imagic flag set.  Clear<y>? yes

Inode 1313468 is in use, but has dtime set.  Fix<y>? yes

and - of course not only once :-( but hundred times

>  >> Same reason (damaged data), I think, prevented reiserfs volume from
>  >> mounting. 
> 
>  PB> yes you're right - but why does it oops when i _only_ want to do an "ls
>  PB> -l"?
> 
> I agree with you, such behaviour is not good, but I do not think
> that you want to run reiserfs on an unstable block device.

it's (mostly) only because of the fschk-times -- this is (or should be)
an 125GB directory tree for music


the next step i'll do ist to give the new kernel (2.4.5) a try (hmm,
eventually with ac4-patch - i've read that there are some
reiserfs-issues are solved ...)


thanks for your attention


: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

      reply	other threads:[~2001-05-31 18:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010528183105.C924@mind.bartosch.net>
2001-05-29 17:10 ` [linux-lvm] Re: [reiserfs-list] lvm-list pointed to reiserfs: fs/lvm-problems? Alexander Zarochentcev
2001-05-29 20:23   ` Peter Bartosch
2001-05-30  9:22     ` Heinz J. Mauelshagen
2001-05-30 11:36     ` Alexander Zarochentcev
2001-05-31 18:40       ` Peter Bartosch [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=20010531204003.A806@mind.bartosch.net \
    --to=peter@bartosch.net \
    --cc=linux-lvm@sistina.com \
    --cc=reiserfs-list@namesys.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