On 9/13/07, Ago <agostino.russo@xxxxxxxxx> wrote:
Douglas McClendon <dmc.fedora <at> filteredperception.org> writes:
> This is I think what I've been noticing as well in a similar situation.
> The one time I tried to recover, fsck _completely_ horked the ext3 fs.
I am no fs expert, but my understanding is:
nested filesystem => forget about the journal in the nested fs
I may be wrong, but I'd guess that VMs suffer the same problem, and the hosted
fs journal can also get corrupted in case of a hard reboot of the hosting
system.
In short I would expect Wubi I/O behavior/performance to be on par or better
than a VM, under all scenarios. BUT in a VM under windows you would use windows
fs driver for the hosting system, while we use ntfs-3g/vfat. So the above
statement assumes that ntfs-3g/vfat behaviour/perfomance is equivalent to the
windows counterpart.
> This was also my first thought. The down side, is that in my usage
> scenario, the fs would be typically on a usb-flash-stick, and it seems
> like an undesirable thing to be writing to it as often as possible,
> rather than periodically.
You can always tweak the scripts affecting sysctl
> Question- are these sysctl settings controlling the writes from the
> hosted-fs-≥host-fs, or from the host-fs-≥disk, or both?
Should be both since that affects the kernel.
> This sounds like it could be fixed with smarter ordering. Do you
> foresee that, or is it for some reason a more-or-less unfixable problem?
Yes Ubuntu kernel hackers have been looking into this, there was just no time
to do it for the 7.10 release, it will probably be fixed for the next release.
But that is beyond my skills.
Regards,
Ago
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
