Re: [reiserfs-list] Re: ReiserFS - corrupted files (2.4.3)

Hans Reiser (reiser@namesys.com)
Mon, 02 Apr 2001 11:58:54 +0400


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 ] -
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/