From: eazgwmir@umail.furryterror.org (Zygo Blaxell)
To: reiserfs-list@namesys.com
Subject: Re: How to break a reiserfs on Linux 2.4.20
Date: 14 Jan 2003 17:39:44 -0500 [thread overview]
Message-ID: <b023jg$519$1@satsuki.furryterror.org> (raw)
In-Reply-To: 15908.25054.542735.558616@laputa.namesys.com
In article <15908.25054.542735.558616@laputa.namesys.com>,
Nikita Danilov <Nikita@Namesys.COM> wrote:
>Zygo Blaxell writes:
> > In article <15908.17236.966170.982897@laputa.namesys.com>,
> > Nikita Danilov <Nikita@Namesys.COM> wrote:
> > >By the way, do you have REISERFS_CHECK compiled in?
> > No. I presume I should try again with it enabled, and see if it says
> > anything interesting?
>That would be helpful.
I ran the script again and started getting Permission denied's after
20 minutes. The kernel said:
Jan 14 17:13:07 berkelium kernel: reiserfs:warning: CONFIG_REISERFS_CHECK is set ON
Jan 14 17:13:07 berkelium kernel: reiserfs:warning: - it is slow mode for debugging.
Jan 14 17:13:07 berkelium kernel: reiserfs: checking transaction log (device 16:02) ...
Jan 14 17:13:08 berkelium kernel: journal-1225: No valid transactions found
Jan 14 17:13:08 berkelium kernel: journal-1299: Setting newest_mount_id to 10
Jan 14 17:13:08 berkelium kernel: Using r5 hash to sort names
Jan 14 17:13:08 berkelium kernel: ReiserFS version 3.6.25
...and that's all, even when repeatedly accessing and trying to
delete the offending names that point to nowhere.
--
Zygo Blaxell (Laptop) <zblaxell@feedme.hungrycats.org>
GPG = D13D 6651 F446 9787 600B AD1E CCF3 6F93 2823 44AD
next prev parent reply other threads:[~2003-01-14 22:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 19:30 2.4.20, reiserfs, md linear, and "Permission denied" Zygo Blaxell
2003-01-14 0:37 ` Zygo Blaxell
2003-01-14 16:56 ` How to break a reiserfs on Linux 2.4.20 Zygo Blaxell
2003-01-14 17:05 ` Nikita Danilov
2003-01-14 19:04 ` Zygo Blaxell
2003-01-14 19:15 ` Nikita Danilov
2003-01-14 22:39 ` Zygo Blaxell [this message]
2003-01-15 22:44 ` Zygo Blaxell
2003-01-16 7:49 ` Oleg Drokin
2003-01-16 14:16 ` Zygo Blaxell
2003-01-16 15:22 ` Oleg Drokin
2003-01-16 15:29 ` Chris Mason
2003-01-16 15:32 ` Oleg Drokin
2003-01-17 20:13 ` Zygo Blaxell
2003-01-14 17:53 ` Oleg Drokin
2003-01-14 19:02 ` Zygo Blaxell
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='b023jg$519$1@satsuki.furryterror.org' \
--to=eazgwmir@umail.furryterror.org \
--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.