All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Krause <manuel.krause@mb.tu-ilmenau.de>
To: reiserfs-list <reiserfs-list@namesys.com>
Subject: Question on IICACHE and mount info (2.4.19-pre5)
Date: Fri, 05 Apr 2002 02:00:03 +0200	[thread overview]
Message-ID: <3CACE903.30901@mb.tu-ilmenau.de> (raw)

Hi!

Is there only the addidional mount option "iicache" with this patch:
ftp://ftp.namesys.com/pub/reiserfs-for-2.4/testing/linux-2.4.19p4-iicache-new-5.patch 
?

There were some more in the early versions of iicache, IIRC.

But at the moment it works very well with 2.4.19-pre5 + 
rml.preempt+lock-break + aa.vm-33 + some other aa patches and some akpm 
ones.

When I put ",iicache" to the fstab lines of my reiserfs partitions I 
don't get a response from

# cat "/proc/fs/reiserfs/ide0(3,11)/super"
state:  REISERFS_VALID_FS
mount options:  BORDER NO_TAILS LOG
...

# cat "/proc/fs/reiserfs/ide0(3,7)/super"
state:  REISERFS_VALID_FS
mount options:  BORDER NO_TAILS LOG
...

# cat /proc/mounts
/dev/root / reiserfs rw,noatime 0 0
/dev/hda11 /mnt/beta reiserfs rw,noatime,nosuid,nodev 0 0
...

only # mount says:
/dev/hda7 on / type reiserfs (rw,noatime,notail,iicache)
...
/dev/hda11 on /mnt/beta type reiserfs 
(rw,nosuid,nodev,noatime,notail,iicache)
...

Seems like some things have gone with the latest patches which worked 
before? It's o.k., of course, if "iicache" doesn't show up for now, I 
know it's for testing only (yes, it would be very nice!). But the 
"notail" thing worked before!


Best regards,

Manuel



             reply	other threads:[~2002-04-05  0:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-05  0:00 Manuel Krause [this message]
2002-04-05  5:02 ` Question on IICACHE and mount info (2.4.19-pre5) Oleg Drokin
2002-04-05 13:27   ` Manuel Krause
2002-04-05 13:37     ` Oleg Drokin
2002-04-08 11:44   ` Manuel Krause
2002-04-08 12:02     ` Oleg Drokin
2002-04-08 12:45       ` Manuel Krause
2002-04-08 12:57         ` Nikita Danilov
2002-04-08 12:59         ` Oleg Drokin
2002-04-08 15:02           ` Hans Reiser
2002-04-05 12:50 ` Yury Yu. Rupasov

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=3CACE903.30901@mb.tu-ilmenau.de \
    --to=manuel.krause@mb.tu-ilmenau.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.