mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: Nikita Danilov <Nikita@namesys.com>,
	Andreas Dilger <adilger@turbolabs.com>
Cc: ReiserFS List <reiserfs-list@namesys.com>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [reiserfs-list] Re: [REISERFS TESTING] new patches on ftp.namesys.com: 2.4.15-pre7
Date: Wed, 21 Nov 2001 11:24:50 +0100	[thread overview]
Message-ID: <20011121102517Z281563-17408+16912@vger.kernel.org> (raw)
In-Reply-To: <200111210110.fAL1Atc11275@beta.namesys.com> <20011121011655.M1308@lynx.no> <15355.31671.983925.611542@beta.reiserfs.com>
In-Reply-To: <15355.31671.983925.611542@beta.reiserfs.com>

Am Mittwoch, 21. November 2001 11:02 schrieb Nikita Danilov:

> Yes, it's right, but currently we have what we have currently. I am
> going to extend inode-attrs.patch and add new mount option
> "noattrs". With it ioctls to set and get attributes will continue to
> work, but attributes themselves will not have any effect. Then, one can
> boot with "rootflags=noattrs" and read-write root, clear all attributes
> by chattr -R and remount root.
>
> I put new version of the patch in the same place, Dieter, can you please
> try it?

So here it goes.
You made one mistake in your README file:

[-]
        chattr -R -SAadiscu /reiserfs-mount-point

    for each reiserfs file system. Said garbage on root file-system can
    prevent system from booting (for example spurious immutable flag on
    /dev/console) to work around this, new mount option
    "noattrs" is provided. With it chattr and lsattr still work, but
    attributes don't have any actual effect. So, boot system with
        "rootflags=noattr", clear all attributes and reboot or remount root
        file system.
[-]

You've forgotten the little "s"  but had it right in your post.

After I've 'booted  into single user mode with "linux rootflags=noattrs" I 
could change my archives but _NOT_ /dev/console the right way. After the 
second reboot I got the warning and kernel hang, again. Something wrong with 
your patch or my installation?

SunWave1 /# l /dev/console
crw-------    1 root     root       5,   1 Nov 21 11:01 /dev/console
SunWave1 /# lsattr /dev/console
lsattr: Invalid argument While reading flags on /dev/console

Two other FS in /dev have some problems, too. But I think that is right.

SunWave1 /# chattr -R -SAadiscu /dev/
chattr: Inappropriate ioctl for device while reading flags on /dev//pts
chattr: Inappropriate ioctl for device while reading flags on /dev//shm

All the files in /proc show the same.

Here comes a little positive example, I think.

SunWave1 /# lsattr /tmp/
----------X-j /tmp//xwlog
--------B-X-j /tmp//kde-nuetzel
------------- /tmp//dcop6SKhoM
---------D-Ej /tmp//YaST2.tdir
----------XEj /tmp//ksocket-root
--------B-X-j /tmp//mcop-nuetzel
--------B--Ej /tmp//kde-root
--------B-X-j /tmp//ksocket-nuetzel
--------B--Ej /tmp//INSTALL
--------BD-Ej /tmp//modules.conf.-
---------DX-j /tmp//vi.recover
--------BD-Ej /tmp//mcop-root
------------j /tmp//lost+found
--------BD-Ej /tmp//modules.conf

What next?

Thanks,
	Dieter

PS Have you read about the latest ACL discussion on LKML?

  reply	other threads:[~2001-11-21 10:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200111210110.fAL1Atc11275@beta.namesys.com>
2001-11-21  8:49 ` Nikita Danilov
2001-11-21  8:16   ` [reiserfs-list] " Andreas Dilger
2001-11-21 12:58     ` Ed Tomlinson
2001-11-21 23:30     ` Stuart Young
2001-11-21 10:02   ` Nikita Danilov
2001-11-21 10:24     ` Dieter Nützel [this message]
2001-11-21 12:18     ` Nikita Danilov
2001-11-21 16:52       ` Jeff Mahoney

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=20011121102517Z281563-17408+16912@vger.kernel.org \
    --to=dieter.nuetzel@hamburg.de \
    --cc=Nikita@namesys.com \
    --cc=adilger@turbolabs.com \
    --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

all inboxes | Powered by JetHome®