From: Nick Urbanik <nicku@vtc.edu.hk>
Cc: reiserfs-list@namesys.com
Subject: Re: on-disk bitmap does not match to the correct one
Date: Fri, 05 Apr 2002 09:35:34 +0800 [thread overview]
Message-ID: <3CACFF66.5361BD3@vtc.edu.hk> (raw)
In-Reply-To: 20020404085310.A5629@namesys.com
Oleg Drokin wrote:
> Hello!
>
> On Thu, Apr 04, 2002 at 05:09:56AM +0800, Nick Urbanik wrote:
> > > Bitmaps are maps with which FS is tracking blocks usage.
> > > If you are running kernel 2.4.16 or older, this might be because
> > > some aplication deleted some files, but still have the files open,
> > > andthen crash occured.
> > > 2.4.16 or earlier kernels are not recommended to use.
> > I have been using 2.4.19-pre5, though I had a couple of crashes over the
> > years with earlier 2.4.x kernels.
> > So what should/can I do about this mismatch?
>
> Get latest reiserfsprogs package (3.x.1b) and run reiserfsck --rebuild-tree
> on your partition.
Beautiful! It worked! While I was at it, I did a lot of LVM volume resizing,
and at one stage lost the root directory of my /var/ftp partition, but
thankfully (wipes panicky sweat from brow!!!!), reiserfsck --rebuild-tree
rebuilt it successfully.
The spec file in the tarball made building an RPM package a snap; it's really
well written.
Thank you very much, Oleg. As we say in Australia, "Your blood's worth
bottling!" :-)
--
Nick Urbanik RHCE nicku@vtc.edu.hk
Dept. of Information & Communications Technology
Hong Kong Institute of Vocational Education (Tsing Yi)
Tel: (852) 2436 8576, (852) 2436 8579 Fax: (852) 2436 8526
PGP: 53 B6 6D 73 52 EE 1F EE EC F8 21 98 45 1C 23 7B ID: 7529555D
GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24
prev parent reply other threads:[~2002-04-05 1:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 10:19 on-disk bitmap does not match to the correct one Nick Urbanik
2002-04-03 11:20 ` Oleg Drokin
2002-04-03 21:09 ` Nick Urbanik
2002-04-04 4:53 ` Oleg Drokin
2002-04-05 1:35 ` Nick Urbanik [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=3CACFF66.5361BD3@vtc.edu.hk \
--to=nicku@vtc.edu.hk \
--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.