linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maciej Soltysiak <solt2@dns.toxicfilms.tv>
To: "Vladimir V. Saveliev" <vs@namesys.com>
Cc: linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: 2.6.15 reiserfs bugs that cause the system to hang and increase load sistematically
Date: Fri, 27 Jan 2006 21:21:47 +0100	[thread overview]
Message-ID: <166928002.20060127212147@dns.toxicfilms.tv> (raw)

Hello Vladimir,

Friday, January 27, 2006, 2:26:48 PM, you wrote:

> On Thu, 2006-01-26 at 21:10 +0100, Maciej Soltysiak wrote:
>> Hello!
>> 
>> I just hit a problem with reiserfs. While working this popped on the console:
>> ReiserFS: sdb2: warning: vs-13060: reiserfs_update_sd: stat data of object [2497 4756 0x0 SD] (nlink == 2) not found (pos 1)
>> ReiserFS: sdb2: warning: zam-7002:reiserfs_add_entry: "reiserfs_find_entry" has returned unexpected value (3)
>> REISERFS: panic (device sdb2): vs-7050: new entry is found, new inode == 0
>> 

> rename encountered "hidden" name when it should not be there.
> the attached patch should make reiserfs to not panic but return -EIO.
Ok, I'll apply that patch and be on the lookout for this warning.

> It would be interesting to know how did you manage to create hidden
> names.
Well on this partition hidden names could have been created either by:
a) bash, and mc with files like .bash_history, etc.. (all standard stuff)
b) courier-imap which creates directories for IMAP folders, like:
   .My Folder
   .Sent
   .Trash

For now, I have no clues about it.

> you should reiserfsck /dev/sdb2
Sure thing.

Thanks a lot.
Maciej



             reply	other threads:[~2006-01-27 20:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-27 20:21 Maciej Soltysiak [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-26 20:10 2.6.15 reiserfs bugs that cause the system to hang and increase load sistematically Maciej Soltysiak
2006-01-27 13:26 ` Vladimir V. Saveliev

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=166928002.20060127212147@dns.toxicfilms.tv \
    --to=solt2@dns.toxicfilms.tv \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-list@namesys.com \
    --cc=vs@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;
as well as URLs for NNTP newsgroup(s).