| To: | Dmitry Monakhov <dmonakhov@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 7/8] xfstests: add a new test that runs fsstress under ENOSPC conditions |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Wed, 2 Nov 2011 15:53:58 -0400 |
| Cc: | linux-fsdevel@xxxxxxxxxxxxxxx, aelder@xxxxxxx, hch@xxxxxx, xfs@xxxxxxxxxxx |
| In-reply-to: | <1319849297-3506-8-git-send-email-dmonakhov@xxxxxxxxxx> |
| References: | <1319849297-3506-1-git-send-email-dmonakhov@xxxxxxxxxx> <1319849297-3506-8-git-send-email-dmonakhov@xxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Sat, Oct 29, 2011 at 04:48:16AM +0400, Dmitry Monakhov wrote: > During stress testing we want to cover as much code paths as possible > fsstress is very good for this purpose. But it has expandable nature > (disk usage almost continually grow). So once it goes in no ENOSPC > condition it will be where till the end. But by running 'dd' writers > in parallel we can regularly trigger ENOSPC but only for a limited > periods of time because each time it opens the same file with O_TRUNC. This fails for me on XFS because the fsstress process has already finished by the time you try to kill it: --- 266.out 2011-11-02 19:46:27.000000000 +0000 +++ 266.out.bad 2011-11-02 19:48:33.000000000 +0000 @@ -3,3 +3,4 @@ Run fsstress Run dd writers in parallel +./266: line 60: kill: (3403) - No such process |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] Fix possible memory corruption in xfs_readlink, Christoph Hellwig |
|---|---|
| Next by Date: | Re: [PATCH 6/8] xfstests: add fiemap operation to fsstress, Christoph Hellwig |
| Previous by Thread: | world wide gaming even when you lose you win, admin |
| Next by Thread: | Re: [PATCH 7/8] xfstests: add a new test that runs fsstress under ENOSPC conditions, Dmitry Monakhov |
| Indexes: | [Date] [Thread] [Top] [All Lists] |