Hi,
On Thu, Oct 19, 2000 at 07:03:54PM +0200, Jan Kara wrote:
>
> > I stumbled into another problem:
> > When using ext3 with quotas the kjournald process stops responding and
> > stays in DW state when the filesystem gets under heavy load. It is easy
> > to reproduce:
> > Just extract two or three larger tar.gz files at the same time to a ext3
> > filesystem with activated quotas...
Which ext3 version, exactly? 0.0.2f had quota problems because ext3
wasn't doing quota writethrough, so that inode cleaning could force
out random dirty quotas at any point. 0.0.3b should fix that. If it
doesn't, I'll try to reproduce it here.
> My suspition is that there is quota enabled on journal and write_dquot()
> deadlocks as to write dquot we need to journal and to journal we need
> to update quota which is locked for writing :(.
Possible in 0.0.2f, but in 0.0.3b all of the quota updates should be
flushed in the context of the calling transaction. Such updates are
always accounted for in the worst-case calculations of how many
journal blocks a transaction might need.
--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
