[Top] [All Lists]

Re: [PATCH 3/3] [XFSQA] Test writing to ENOSPC

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: [PATCH 3/3] [XFSQA] Test writing to ENOSPC
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Mon, 16 Mar 2009 02:27:06 -0400
Cc: xfs@xxxxxxxxxxx
In-reply-to: <1237114181-18431-4-git-send-email-david@xxxxxxxxxxxxx>
References: <1237114181-18431-1-git-send-email-david@xxxxxxxxxxxxx> <1237114181-18431-4-git-send-email-david@xxxxxxxxxxxxx>
User-agent: Mutt/1.5.18 (2008-05-17)
On Sun, Mar 15, 2009 at 09:49:41PM +1100, Dave Chinner wrote:
> Use larger files and different writing styles to fill
> a 100MB filesystem to being full. In each case we should
> get very close to the filesystem being full before getting
> ENOSPC. THis tests different types of ENOSPC failures to
> test 203 and requires more changes to pass.

Looks good.   But don't we actually need a trap handler to unmount the
scratch partitions if the test gets intterupted?  I always added them
to my tests, copying that fragment from older patches.  (also applies
to the previous patch)

<Prev in Thread] Current Thread [Next in Thread>