From: liqui-D-read <liquid@nano.cz>
To: reiserfs-mailing-list <reiserfs-list@namesys.com>
Subject: reiserfs+LVM+loopAES
Date: 07 Nov 2002 11:21:31 +0100 [thread overview]
Message-ID: <1036664491.13120.38.camel@ceros> (raw)
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
hello
i've got a following setup:
Linux base 2.4.19 #2 Thu Nov 7 09:57:09 CET 2002 i686 unknown
it's debian woody 3.0
there's a LVM and loopAES in kernel also.
the LVM disc is mounted via loop to make an encryption.
everything worked fine, but one day i wasn't able to read some data from
that filesystem. so unmounted it and ... attached it via losetup.
(sorry for offtopic ... now comes the real part)
root@base:/tmp# reiserfsck --fix-fixable /dev/loop1
<-------------reiserfsck, 2002------------->
reiserfsprogs 3.x.1b
Will check consistency of the filesystem on /dev/loop1
Will fix what can be fixed w/o --rebuild-tree
Will put log info to 'stdout'
Do you want to run this program?[N/Yes] (note need to type Yes):Yes
###########
reiserfsck --fix-fixable started at Thu Nov 7 10:59:36 2002
###########
Replaying journal..
0 transactions replayed
Checking S+tree../ 4 (of 6)/ 18 (of 127)/138 (of 155)bit 90843826,
bitsize 90840576
reiserfsck: bitmap.c:160: reiserfs_bitmap_test_bit: Assertion
`bit_number < bm->bm_bit_size' failed.
Aborted
kernel doesn't report any bugs/errors
i don't know if it isn't a LVM or AESloop bug, but i've got last
versions of both.
please help :)
l.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2002-11-07 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-07 10:21 liqui-D-read [this message]
2002-11-18 8:01 ` reiserfs+LVM+loopAES 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=1036664491.13120.38.camel@ceros \
--to=liquid@nano.cz \
--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.