-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <alpine.LSU.2.00.0909242054411.5038@nimrodel.valinor> On Thursday, 2009-09-24 at 08:57 +0200, Takashi Iwai wrote:
At Wed, 23 Sep 2009 17:52:38 -0700, Jeff Mahoney wrote:
ReiserFS hasn't really changed and neither has grub. Rafael's diagnosis in the bugzilla entry is probably right though. It's probably replaying the journal, which really just means traversing it and building a mapping table. It doesn't actually write anything. The big problem to figure out is why it's leaving loads of open transactions open in the journal for an operation that should be "clean."
Notice that the problem I reported is grub being very slow in loading the kernel. Once the the initial kernel starts booting, it boots fast, it sees the loaded swap partition and reload the swapped out system, fast. You can watch the sequence in the video I recorded. And the weird thing with your explanation is that grub should not replay the log, should it? I thought that was something reserved for reiserfsck during init?
IIRC, it's just a long-standing issue of reiserfs support in GRUB. After S2D, it's still not 100% "clean" as GRUB believes, so it replays journal.
Can grub replay the journal? :-?
The best solution would be to fix/improve GRUB, but this would happen unlikely. A classical solution is to create only a small /boot partition with ext2 or ext3 and the rest with reiserfs.
Yes, that is what I'll try this weekend, time permitting: I'll move /boot to a separate ext2 partition (which I have available) and report back; I just wanted to warn people using reiserfs as root filesystem that there may be problems. And IMO, YaST should warn. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkq7w2MACgkQtTMYHG2NR9WdQACePdbM63W1T2hlT9D3XcShCc/Y tKgAmwRq7nB0Nrq+3DvB7EHw20WSjHFU =2kXl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org