| To: | Steve Lord <lord@xxxxxxx> |
|---|---|
| Subject: | Re: XFS assertion failed: tp->t_blk_res_used <= tp->t_blk_res, file: xfs_trans.c, line: 335 |
| From: | KELEMEN Peter <fuji@xxxxxxx> |
| Date: | Mon, 9 Apr 2001 14:31:32 +0200 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <200104072146.f37LkLu11686@xxxxxxxxxxxxxxxxxxxx>; from lord@xxxxxxx on Sat, Apr 07, 2001 at 04:46:21PM -0500 |
| Organization: | ELTE Eotvos Lorand University of Sciences, Budapest, Hungary |
| References: | <20010407214610.A1436@xxxxxxxxxxxxxx> <200104072146.f37LkLu11686@xxxxxxxxxxxxxxxxxxxx> |
| Reply-to: | KELEMEN Peter <fuji@xxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
* Steve Lord (lord@xxxxxxx) [20010407 16:46]:
> We had a few days this week between good trees, I broke it on
> Monday or Tuesday and the fix for this was checked in on the
> 5th.
Confirmed. 04/09 tree works fine.
> The repair output would probably disappear after a mount of the
> filesystem.
Indeed.
> Repair does not take into account replaying the log, only
> mounting the filesystem would do this.
Is there any (planned) way of forcing (virtual) log replay?
Peter
--
.+'''+. .+'''+. .+'''+. .+'''+. .+''
Kelemen Péter / \ / \ / fuji@xxxxxxx
.+' `+...+' `+...+' `+...+' `+...+'
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: linux-2.4-xfs build broken, Aaron Lehmann |
|---|---|
| Next by Date: | Re: shutdown umount hangs, Utz Lehmann |
| Previous by Thread: | Re: XFS assertion failed: tp->t_blk_res_used <= tp->t_blk_res, file: xfs_trans.c, line: 335, Steve Lord |
| Next by Thread: | 2.4.3-xfs oops, Lennert Buytenhek |
| Indexes: | [Date] [Thread] [Top] [All Lists] |