public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mikko C." <mikko.cal@gmail.com>
To: Kernel development list <linux-kernel@vger.kernel.org>
Subject: reiserfs regression since rc3?
Date: Fri, 01 May 2009 17:34:47 +0200	[thread overview]
Message-ID: <49FB1697.1060909@gmail.com> (raw)

This happens since 2.6.30-rc3. Didn't happen with rc2 and previous.


REISERFS (device sda9): found reiserfs format "3.6" with standard 
journal                                                   
REISERFS (device sda9): using ordered data 
mode                                                                              

REISERFS (device sda9): journal params: device sda9, size 8192, journal 
first block 18, max trans len 1024, max batch 900, max commit age 30, 
max trans age 
30                                                                                            

REISERFS (device sda9): checking transaction log 
(sda9)                                                                     
REISERFS (device sda9): Using r5 hash to sort 
names                                                                          

------------[ cut here 
]------------                                                                                         

WARNING: at fs/namei.c:1251 
lookup_one_len+0xda/0xf0()                                                                       

Hardware name: 
MM061                                                                                                         

Modules linked in: coretemp hwmon cpufreq_ondemand fan iwl3945 iwlcore 
snd_hda_codec_idt usb_storage snd_hda_intel mac80211 snd_hda_codec 
led_class snd_pcm snd_timer snd cfg80211 psmouse evdev soundcore 
uhci_hcd ehci_hcd snd_page_alloc ac button battery 
thermal                                                                                                                  

Pid: 1551, comm: mount Not tainted 2.6.30-rc4 
#1                                                                             

Call 
Trace:                                                                                                                  

 [<ffffffff802389ba>] ? 
warn_slowpath+0xea/0x160                                                                             

 [<ffffffff80533270>] ? 
printk+0x4e/0x56                                                                                     

 [<ffffffff8030be2a>] ? 
prepare_error_buf+0x52a/0x620                                                                        

 [<ffffffff803181b2>] ? 
do_journal_end+0x292/0xf40                                                                           

 [<ffffffff803192e9>] ? 
do_journal_begin_r+0x159/0x330                                                                       

 [<ffffffff802abafa>] ? 
lookup_one_len+0xda/0xf0                                                                             

 [<ffffffff8031d0cd>] ? 
reiserfs_xattr_init+0x3d/0xb0                                                                        

 [<ffffffff8030a8b5>] ? 
reiserfs_fill_super+0x835/0xb60                                                                      

 [<ffffffff8029cc68>] ? 
kmem_cache_alloc+0x68/0xa0                                                                           

 [<ffffffff802a371a>] ? 
sget+0x3ca/0x410                                                                                     

 [<ffffffff802a4044>] ? 
get_sb_bdev+0x174/0x1a0                                                                              

 [<ffffffff8030a080>] ? 
reiserfs_fill_super+0x0/0xb60                                                                        

 [<ffffffff802a2ab6>] ? 
vfs_kern_mount+0x56/0xd0                                                                             

 [<ffffffff802a2b93>] ? 
do_kern_mount+0x53/0x120                                                                             

 [<ffffffff802bbcca>] ? 
do_mount+0x2ba/0x8c0                                                                                 

 [<ffffffff802bc39d>] ? 
sys_mount+0xcd/0x100                                                                                 

 [<ffffffff8020b42b>] ? 
system_call_fastpath+0x16/0x1b                                                                       

---[ end trace 58726f3f2c919bd3 ]---

Entry in /etc/fstab:
/dev/sda9        /usr/portage    reiserfs        noatime,notail  0 0

Sorry if it's been reported already, I couldn't find it.
I'm not subscribed so please CC me if you answer.
Thanks.

Mikko

                 reply	other threads:[~2009-05-01 15:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=49FB1697.1060909@gmail.com \
    --to=mikko.cal@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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