All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antonio <tritemio@gmail.com>
To: reiserfs-list@namesys.com
Subject: Re: reiserfs corruption
Date: Thu, 26 Jan 2006 15:58:41 +0100	[thread overview]
Message-ID: <5486cca80601260658o33bdc9f3n@mail.gmail.com> (raw)
In-Reply-To: <1138282968.6313.113.camel@tribesman.namesys.com>

Hi,

2006/1/26, Vladimir V. Saveliev <vs@namesys.com>:
[cut]
> > The first time I ran "reisefsck --rebuidl-tree" and corrected all the
> > errors. After few day I had again those errors, so I thinked that my
> > HD was at the end of his life. However I have another debian system on
> > the same disk that works without problems.
>
> is it on reiserfs?
> would you, please, show output of
> fdisk -l /dev/hda

No, the only reiserfs partition is hda9 which is the root partition of
one of the two debian systems I have on this machine.

As you requested:
# fdisk -l /dev/hda

Disk /dev/hda: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1               1         382     3068383+   7  HPFS/NTFS
/dev/hda2   *         383         393       88357+  83  Linux
/dev/hda3             394        1122     5855692+  83  Linux
/dev/hda4            1123        7297    49600687+   5  Extended
/dev/hda5            1123        1851     5855661   83  Linux
/dev/hda6            1852        1915      514048+  82  Linux swap / Solaris
/dev/hda7            1916        5562    29294496   83  Linux
/dev/hda8            5563        6413     6835626   83  Linux
/dev/hda9   *        6414        7297     7100698+  83  Linux

> Would you, please, downgrade to 2.6.14 (or whatever kernel you used
> before 2.6.15.1) and see whether the problem comes up.

Yes. I'm yet running the standard debian etch kernel 2.6.12. No
problem so far (~ 1 hour), but it's too early too say if this resolved
the problem. Even with the 2.6.15.1 kernel the system worked for days
before having problems.

I'll update you the situation as far as I get an error or otherwise tomorrow.

Thanks for the reply.

Best Regards,

  ~ Antonio

  reply	other threads:[~2006-01-26 14:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-26 10:49 reiserfs corruption Antonio
2006-01-26 13:42 ` Vladimir V. Saveliev
2006-01-26 14:58   ` Antonio [this message]
2006-01-27 14:17     ` Antonio
  -- strict thread matches above, loose matches on Subject: below --
2002-11-16 22:35 Nick Wellnhofer
2002-11-18  8:12 ` Oleg Drokin

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=5486cca80601260658o33bdc9f3n@mail.gmail.com \
    --to=tritemio@gmail.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 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.