From: Hans Reiser <reiser@namesys.com>
To: "Rasmus BЬg Hansen" <moffe@amagerkollegiet.dk>
Cc: linux-kernel@vger.kernel.org,
ReiserFS Mailing List <reiserfs-list@namesys.com>,
Robert NEDBAL <R.Nedbal@sh.cvut.cz>,
reiserfs-dev@namesys.com
Subject: Re: [reiserfs-list] Re: ReiserFS - corrupted files (2.4.3)
Date: Mon, 02 Apr 2001 11:58:54 +0400 [thread overview]
Message-ID: <3AC8313E.DF217C0E@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0104021821500.989-100000@7812-grignard.amagerkollegiet.dk>
monstr will debug this and elena will enter it into our buglist file.
Hans
Rasmus BЬg Hansen wrote:
>
> Hello
>
> I am getting musch the same types of corruption. I am on a K6-2 with a
> 30Gb IBM HD and 256Mb RAM running vanilla 2.4.3 with iptables and squid
> caching proxy. The problems arise on the cache part of the FS (i.e. with
> many file operations).
>
> I am considering using reiserfsck (3.x.0j) to fix it, but it has to wait
> until the morning - so in the meantime perhaps somebody can use the info
> about the corruptions? I have nowhere to back up my rather large (in
> comparison to other space on the box) cache, but if it goes lost in the
> process of rebuilding it, it does not matter so much.
>
> What should I do to help? I will try to debug the problem if necessary -
> should I turb on internal checks?
>
> On Mon, 2 Apr 2001, Robert NEDBAL wrote:
>
> > Hello,
> > I'm using ReiserFS on my primary filesystem and yesterday, I have found
> > that some files are corrupted. Yesterday I had to reset computer becase
> > X Window freezed. Maybe it caused this problem.
> >
> > This comes from log:
>
> [SNIP]
>
> My log goes much the same (although I have fewer errors - it seems to
> affect only few files):
> Mar 30 10:32:09 wiibroe kernel: reiserfs: checking transaction log
> (device 16:01) ...
> Mar 30 10:32:09 wiibroe kernel: Using r5 hash to sort names
> Mar 30 10:32:09 wiibroe kernel: ReiserFS version 3.6.25
> [...]
> Apr 2 14:36:10 wiibroe kernel: is_leaf: item location seems wrong:
> *OLD*[1214 319934 0x8f1 DIRECT], item_len 0, item_location 0,
> free_space(entry_count) 2289
> Apr 2 14:36:10 wiibroe kernel: vs-5150: search_by_key: invalid format
> found in block 132193. Fsck?
> Apr 2 14:36:10 wiibroe kernel: is_leaf: item location seems wrong:
> *OLD*[1214 319934 0x8f1 DIRECT], item_len 0, item_location 0,
> free_space(entry_count) 2289
> Apr 2 14:36:10 wiibroe kernel: vs-5150: search_by_key: invalid format
> found in block 132193. Fsck?
> Apr 2 14:36:10 wiibroe kernel: vs-13050: reiserfs_update_sd: i/o
> failure occurred trying to update [1214 319936 0x0 SD] stat datais_leaf:
> item location seems wrong: *OLD*[1214 319934 0x8f1 DIRECT], item_len 0,
> item_location 0, free_space(entry_count) 2289
> Apr 2 14:36:10 wiibroe kernel: vs-5150: search_by_key: invalid format
> found in block 132193. Fsck?
> Apr 2 14:36:10 wiibroe kernel: vs-: reiserfs_delete_solid_item: i/o
> failure occurred trying to delete [1214 319936 0x0 SD]
> [...]
> Apr 2 18:36:25 wiibroe kernel: vs-13042: reiserfs_read_inode2: [1020
> 271248 0x0 SD] not found
> Apr 2 18:36:25 wiibroe kernel: vs-13048: reiserfs_iget: bad_inode. Stat
> data of (1020 271248) not found
> Apr 2 18:36:50 wiibroe kernel: is_leaf: item location seems wrong:
> *OLD*[1214 319934 0x8f1 DIRECT], item_len 0, item_location 0,
> free_space(entry_count) 2289
> Apr 2 18:36:50 wiibroe kernel: vs-5150: search_by_key: invalid format
> found in block 132193. Fsck?
> Apr 2 18:36:50 wiibroe kernel: vs-13070: reiserfs_read_inode2: i/o
> failure occurred trying to find stat data of [1214 319935 0x0 SD]
> Apr 2 18:36:50 wiibroe kernel: vs-13048: reiserfs_iget: bad_inode. Stat
> data of (1214 319935) not found
>
> > When I want to list corrupted directory, I get this:
>
> What I get is:
>
> root@wiibroe:/var/spool/squid# find /var/spool/squid/ -type f | xargs ls
> > /dev/null
> find: /var/spool/squid/01/C5/0001C5DA: Ingen sЕdan fil eller filkatalog
> find: /var/spool/squid/01/C5/0001C5E6: Ingen sЕdan fil eller filkatalog
> find: /var/spool/squid/03/F5/0003F5E9: Adgang nФgtet
> find: /var/spool/squid/04/B6/0004B6E0: Adgang nФgtet
>
> (Ingen sЕdan fil eller filkatalog = No such file or directory
> Adgang nФgtet = Access denied)
>
> Rasmus BЬg Hansen
>
> --
> -- [ Rasmus 'MЬffe' BЬg Hansen ] --------------------------------------
> if (getenv(EDITOR) == "vim") {karma++};
> --------------------------------- [ moffe at amagerkollegiet dot dk ] -
prev parent reply other threads:[~2001-04-02 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-02 12:04 ReiserFS - corrupted files (2.4.3) Robert NEDBAL
2001-04-02 15:54 ` Nicholas Petreley
[not found] ` <Pine.BSF.4.31.0104021921380.36074-100000@veverka.sh.cvut.cz>
2001-04-02 18:12 ` Nicholas Petreley
2001-04-02 16:41 ` Rasmus Bøg Hansen
2001-04-02 7:58 ` Hans Reiser [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=3AC8313E.DF217C0E@namesys.com \
--to=reiser@namesys.com \
--cc=R.Nedbal@sh.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=moffe@amagerkollegiet.dk \
--cc=reiserfs-dev@namesys.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