public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nikita Danilov <Nikita@Namesys.COM>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: ReiserFS List <reiserfs-list@Namesys.COM>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [REISERFS TESTING] new patches on ftp.namesys.com: 2.4.15-pre7
Date: Wed, 21 Nov 2001 11:49:39 +0300	[thread overview]
Message-ID: <15355.27299.252362.983624@beta.reiserfs.com> (raw)
In-Reply-To: <200111210110.fAL1Atc11275@beta.namesys.com>
In-Reply-To: <200111210110.fAL1Atc11275@beta.namesys.com>

Dieter NЭtzel writes:
 > Sorry Nikita,
 > 
 > but kernel 2.4.15-pre7 + preempt + ReiserFS A-N do _NOT_ boot for me.
 > I've tried it with "old" and "new" (current) N-inode-attrs.patch. But that doesn't matter.
 > 
 > [-]
 > IP: routing cache hash table of 8192 buckets, 64Kbytes
 > TCP: Hash tables configured (established 262144 bind 65536)
 > NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
 > reiserfs: checking transaction log (device 08:03) ...
 > Using r5 hash to sort names
 > ReiserFS version 3.6.25
 > VFS: Mounted root (reiserfs filesystem) readonly.
 > Freeing unused kernel memory: 208k freed
 > "Warning: unable to open an initial console." 

N-inode-attrs.patch uses previously unused field in reiserfs on-disk
inode structure to store inode attributes. It seems that in some cases
this field actually contains garbage. It may happen that you have got
immutable bit for your console device this way.

As a work around try to boot with ext2, do

lsattr /dev/console to check, and run 

chattr -R -SAadiscu /reiserfs-mount-point

for each reiserfs file system to clear all attributes. Yes, it's silly.

 > 
 > SysRq: Show Regs
 > 
 > Pid: 1, comm: init
 > EIP: 0023 : [<0804c842>] CPU: 0 ESP: 002b:bffffe10 EFLAGS: 00010246 Not tainted
 > EAX: ffffffff EBX: bfffff00 ECX: 0000000d EDX: ffffffff
 > ESI: bffffef4 EDI: 00000002 EBP: bffffe78 DS: 002b ES: 002b
 > CR0: 8005003b CR2: 080609c0 CR3: 27adc000 CR4: 000002d0
 > Call Trace:
 > 
 > SysRq: Show State
 > 
 > init, keventd, ksoftirqd_CPU, kswapd, bdflush, kupdated, scsi_eh_0, kreiserfsd
 > 
 > Thanks,
 > 	Dieter
 > -- 
 > Dieter NЭtzel
 > Graduate Student, Computer Science
 > @home: Dieter.Nuetzel@hamburg.de

Nikita.

       reply	other threads:[~2001-11-21  7:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200111210110.fAL1Atc11275@beta.namesys.com>
2001-11-21  8:49 ` Nikita Danilov [this message]
2001-11-21  8:16   ` [reiserfs-list] Re: [REISERFS TESTING] new patches on ftp.namesys.com: 2.4.15-pre7 Andreas Dilger
2001-11-21 10:02     ` Nikita Danilov
2001-11-21 10:24       ` Dieter Nützel
2001-11-21 12:18         ` Nikita Danilov
2001-11-21 16:52           ` Jeff Mahoney
2001-11-21 23:30       ` Stuart Young
2001-11-21 12:58     ` Ed Tomlinson
2001-11-21  1:06 Dieter Nützel
  -- strict thread matches above, loose matches on Subject: below --
2001-11-21  0:47 Dieter Nützel
2001-11-21  0:07 Dieter Nützel
2001-11-21  0:24 ` Stuart Young
2001-11-21  0:36   ` Dieter Nützel
2001-11-20 18:29 Nikita Danilov

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=15355.27299.252362.983624@beta.reiserfs.com \
    --to=nikita@namesys.com \
    --cc=Dieter.Nuetzel@hamburg.de \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox