Re: Strange write starvation on 2.6.17 (and other) kernels

On Tue, 15 Aug 2006, Andrew Morton wrote:

Which filesystem?

If ext3 in ordered-data mode: any fsync() will sync the whole filesystem
(it has to).

Could you explain some more why it has to?... Is this caused by design of ext3 or any filesystem in ordered-data mode has to do it?

Thanks,

Grzegorz Kulewski

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Strange write starvation on 2.6.17 (and other) kernels
    • From: Andrew Morton <[email protected]>

• References:
  • Strange write starvation on 2.6.17 (and other) kernels
    • From: Andrzej Szymanski <[email protected]>
  • Re: Strange write starvation on 2.6.17 (and other) kernels
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: [PATCH 2/2] acpi,backlight: MSI S270 laptop support - driver
• Next by Date: Re: Daily crashes, incorrect RAID behaviour
• Previous by thread: Re: Strange write starvation on 2.6.17 (and other) kernels
• Next by thread: Re: Strange write starvation on 2.6.17 (and other) kernels
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]