mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fabio Coatti <cova@ferrara.linux.it>
To: linux-kernel@vger.kernel.org
Subject: test5 and JFS on /: problems, anyone?
Date: Sat, 13 Sep 2003 19:17:11 +0200	[thread overview]
Message-ID: <200309131917.11731.cova@ferrara.linux.it> (raw)

I'm using JFS on / partition on a couple of machines and when I've installed 
2.6.0-test5 I've got fs corruption on both. I can't say if the problems are 
happened during normal operation or at boot time, but I've noticed it only 
after a reboot. Some files disappeared (i.e. /etc/X11/Xsession), some others 
unreadable or inaccessible to any operation apart ls (lsattr, chattr, chown, 
cat, and so on, with permission denied); for example on both systems 
/var/lock/subsys was missing. Now fsck locks indefinitely at pass 1 and the 
same happens during operations that requires access to some files (i.e. rpm 
--rebuilddb), but ctrl-c works and the process is terminated.
Machines are quite similar but not exactly the same:
P IV on both, one with SMP kernel (for HT processor); on one machine I've got 
jfs utils rev. 1.0.24 and 1.1.2 on the other. 
On the same HW test4 works just fine on this respect, I've recompiled test5 
using the same config of test4 (make oldconfig).
No HW errors on dmesg.
I would like to know if someone else is having problmes with test5 and JFS or 
if this is only bad luck :)
I've still the corrupted FS handy so I can made some checks, if needed.


-- 
Fabio Coatti       http://www.ferrara.linux.it/members/cova     
Ferrara Linux Users Group           http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.


             reply	other threads:[~2003-09-13 17:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-13 17:17 Fabio Coatti [this message]
2003-09-15 17:59 ` Dave Kleikamp

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=200309131917.11731.cova@ferrara.linux.it \
    --to=cova@ferrara.linux.it \
    --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

all inboxes | Powered by JetHome®