From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: Paul Wagland <paul@wagland.net>
Cc: James Neal <jneal@nks.net>, Matt Zimmerman <mdz@debian.org>,
user-mode-linux-devel@lists.sourceforge.net,
256873-forwarded@bugs.debian.org,
Marius Gedminas <mgedmin@b4net.lt>
Subject: Re: [uml-devel] [mgedmin@b4net.lt: Bug#256873: user-mode-linux: fails to start (kernel panic)]
Date: Sat, 3 Jul 2004 19:21:37 +0200 [thread overview]
Message-ID: <200407031921.38522.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <20040701230225.i4p20wsc080g04oc@www.wagland.net>
Alle 23:02, giovedì 1 luglio 2004, Paul Wagland ha scritto:
> On Wed 30 Jun 2004 20:38:41 CEST, BlaisorBlade wrote:
> > Alle 09:56, mercoled? 30 giugno 2004, Paul Wagland ha scritto:
> >> On Jun 30, 2004, at 1:55, James Neal wrote:
> >>
> >> I normally hate doing this... but me too!
> >>
> >> Even worse, it would appear that UML and reiserfs don't play nice...
> >> when the UML does crash I tend to end up with some pretty massive
> >> filesystem corruptions, to the point where my UML will not boot
> >> anymore, and I spent over an hour just now trying to coax it back to
> >> life by copying in and replacing all of the corrupted binaries.
> >
> > If you didn't enable the synchronous UBD access (near to the UBD options
> > in the kernel configuration), that's almost expected, as the help
> > explains (IIRC), for journaled filesystems (although some people claim
> > ext3 does not need it, and this could be true, even because reiserfs
> > works like ext3 "data=writeback" mode, which is less safe than the
> > default ext3
> > "data=ordered").
>
> Ah. Ok, I assume by this you mean that I should be doing ubd1s=blah instead
> of ubd1=blah. I will try that, it looks like it should at least stop the fs
> screwage. On a different sidenote, what is the "recommended" filesystem for
> UML?
Well, I speak about CONFIG_BLK_DEV_UBD_SYNC (Always use synchronous access for
UBD), but maybe what you suggest is the same thing (the kernel option would
turn "s(ync)" on for all UBDs, maybe).
I've no idea of a "recommended" filesystem; I only know that ext3 *seems* not
to require that UBD are accessed in a synchronous way. (I.e. somebody says he
never experienced data loss with ext3 with async UBDs).
Bye
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-07-03 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 18:27 [uml-devel] [mgedmin@b4net.lt: Bug#256873: user-mode-linux: fails to start (kernel panic)] Matt Zimmerman
2004-06-29 19:06 ` BlaisorBlade
2004-06-29 20:34 ` Stefan Gybas
2004-06-29 23:55 ` James Neal
2004-06-30 7:56 ` Paul Wagland
2004-06-30 18:38 ` BlaisorBlade
2004-07-01 21:02 ` Paul Wagland
2004-07-03 17:21 ` BlaisorBlade [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200407031921.38522.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=256873-forwarded@bugs.debian.org \
--cc=jneal@nks.net \
--cc=mdz@debian.org \
--cc=mgedmin@b4net.lt \
--cc=paul@wagland.net \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox