linux-ext4 - Re: ext4 quota tests?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100126183500.GJ3187@quack.suse.cz>
Date:	Tue, 26 Jan 2010 19:35:00 +0100
From:	Jan Kara <jack@...e.cz>
To:	Curt Wohlgemuth <curtw@...gle.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: ext4 quota tests?

  Hi Curt,

On Tue 26-01-10 09:31:24, Curt Wohlgemuth wrote:
> I heard from the ext4 conference call yesterday that you might have
> some quota tests that would be useful.  Can you give me a pointer to
> where I might find them?
  Hum, I have some scripts I use for testing of quota but it's nothing
too clever. What exactly would you like to test? What generally needs to be
tested from filesystem POV (since I guess that's what you're interested in)
is whether quota accounting matches the real usage. So what I do is:

run the load I want to check
quotaoff -vu $mntpoint
repquota -u $mntpoint | sed -ne '6,$p' | tr -s ' ' | sort >before_check
quotacheck -vu $mntpoint
repquota -u $mntpoint | sed -ne '6,$p' | tr -s ' ' | sort >after_check
diff before_check after_check >/dev/null || echo "Quota usage differs!"

For "load I want to check" I usually use fsstress, fsx-linux or similar
programs.

Oh, and when I want to be nasty, I also test load like:
as root do:
  while true; do
    BLOCKLIMIT=$minblimit+$((RANDOM%($maxblimit-$minblimit)))
    INODELIMIT=$minilimit+$((RANDOM%($maxilimit-$minilimit)))
    setquota -u testuser 0 $BLOCKLIMIT 0 $INODELIMIT $mntpoint
    sleep 1
  done

as testuser do:
  while true; do tar xzf some_larger_archive.tar.gz; rm -rf archive; done

Possibly you might also want to run 'sync' in parallel once in a while to
make the mix more interesting. The point is to test whether allocation
failure paths work right...

								Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html