| To: | Andi Kleen <ak@xxxxxx> |
|---|---|
| Subject: | Re: XFS: how to NOT null files on fsck? |
| From: | L A Walsh <lkml@xxxxxxxxx> |
| Date: | Tue, 03 Aug 2004 23:37:39 -0700 |
| Cc: | linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx, nathans@xxxxxxx |
| In-reply-to: | <m3d627bueu.fsf@xxxxxxxxxxxxxxxxxxxxxx> |
| References: | <200407050247.53743.norberto+linux-kernel@xxxxxxxxxxxx> <40EEC9DC.8080501@xxxxxxxxx> <20040729013049.GE800@frodo> <410FDA19.9020805@xxxxxxxxx> <m3d627bueu.fsf@xxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla Thunderbird 0.7.1 (Windows/20040626) |
Not laptop, 2-CPU workstation used as home "server". :-) Andi Kleen wrote: L A Walsh <lkml@xxxxxxxxx> writes:Now I know it takes a while before data may end up on disk and that it may not go out to disk in an ordered fashion, but 2-3 days? This isn't a case of a multi-extent file. My current fstab is only 1335 bytes long. I doubt it has ever been more than 2.Is this perhaps on a laptop? Some scripts for laptop use configure insanely long data flush times to conserve HD spin time. Sometimesit is even completely turned off (laptop mode). The extent flush is dependent on the configured bdflush or pdflushd datatimeouts.The truncate is independent from this because it is flushed with a different path.-Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | xfs 1.3.1 patch for kernel 2.4.19?, Junfeng Yang |
|---|---|
| Next by Date: | ACL-over-XFS patch for 2.4.26 kernels?, Claude-Jacques Tronquet |
| Previous by Thread: | Re: XFS: how to NOT null files on fsck?, Andi Kleen |
| Next by Thread: | xfs 1.3.1 patch for kernel 2.4.19?, Junfeng Yang |
| Indexes: | [Date] [Thread] [Top] [All Lists] |