All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <ext-adrian.hunter@nokia.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Error testing ext3 on brd ramdisk
Date: Fri, 14 Nov 2008 15:25:32 +0200	[thread overview]
Message-ID: <491D7C4C.3090907@nokia.com> (raw)

Hi

I am trying to test EXT3 on a ramdisk and after some number of mounts
(anywhere from 7 to 603 so far), I get errors from e2fsck like this:

/dev/ram0: HTREE directory inode 137 has an invalid root node.
HTREE INDEX CLEARED.
/dev/ram0: Entry 'f1770' in /work/p0/da/d1c61 (137) has deleted/unused inode 692.  CLEARED.
/dev/ram0: Entry 'fa37' in /work/p0/da/d1c61 (137) has deleted/unused inode 799.  CLEARED.
/dev/ram0: Entry 'c1686' in /work/p0/da/d1c61 (137) has deleted/unused inode 470.  CLEARED.
/dev/ram0: Entry 'c19b8' in /work/p0/da/d1c61 (137) has an incorrect filetype (was 3, should be 1).

/dev/ram0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
       (i.e., without -a or -p options)


This is what I do:


modprobe brd rd_nr=1 rd_size=4096
mkfs.ext3 /dev/ram0
dmesg -n8
i=0
while (true); do
	i=`expr $i + 1`
	echo -------------------------------------------------------------
	echo Cycle $i
	date
	echo Mounting
	sleep 1
	mount -t ext3 /dev/ram0 /mnt/test_file_system || exit 1
	echo Removing old fsstress data
	rm -rf /mnt/test_file_system/work
	mkdir /mnt/test_file_system/work || exit 1
	echo Starting fsstress
	fsstress -d /mnt/test_file_system/work -p 3 -l 0 -n 100000000 &
	echo Sleeping 30 seconds
	sleep 30
	echo Stopping fsstress
	while (ps -e | grep fsstress);do
		pkill fsstress
		sleep 1
	done
	echo Unmounting
	umount /mnt/test_file_system || exit 1
	echo Checking
	sleep 1
	e2fsck -fvp /dev/ram0 || exit 1
done


It seems to happen ever since the introduction of brd (Feb '08).

Does anyone know what is going on?

Regards
Adrian


             reply	other threads:[~2008-11-14 13:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14 13:25 Adrian Hunter [this message]
2009-02-27 18:08 ` Error testing ext3 on brd ramdisk Jorge Boncompte [DTI2]
2009-02-28  5:58   ` Nick Piggin
2009-03-02 17:42     ` Jorge Boncompte [DTI2]
2009-03-05  6:55       ` Nick Piggin
2009-03-05  9:19         ` Jorge Boncompte [DTI2]
2009-03-05  9:46           ` Nick Piggin
2009-03-05 10:56             ` Jorge Boncompte [DTI2]
2009-03-05 12:12               ` Jorge Boncompte [DTI2]
2009-03-10 16:12                 ` Nick Piggin
2009-03-10 16:30                   ` Nick Piggin
2009-03-10 16:49                     ` Jorge Boncompte [DTI2]
2009-03-11  2:19                       ` Nick Piggin
2009-03-13 17:06                         ` Jorge Boncompte [DTI2]
2009-03-17  9:40                           ` Denis Karpov
2009-03-18 12:11                             ` Nick Piggin
2009-03-18 13:42                               ` Jan Kara
2009-03-20 12:24                                 ` Denis Karpov
2009-03-20 12:49                                   ` Denis Karpov
2009-03-20 12:49                                     ` Denis Karpov
2009-03-20 13:35                                 ` Denis Karpov
2009-03-05 10:45           ` Nick Piggin
2009-03-05 11:54             ` Jorge Boncompte [DTI2]
2009-03-06  7:47         ` Adrian Hunter
2009-03-10 11:03           ` Nick Piggin

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=491D7C4C.3090907@nokia.com \
    --to=ext-adrian.hunter@nokia.com \
    --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 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.