From: Denis Vlasenko <vda.linux@googlemail.com>
To: "Molle Bestefich" <molle.bestefich@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 corruption
Date: Thu, 10 Aug 2006 09:44:27 +0200 [thread overview]
Message-ID: <200608100944.27396.vda.linux@googlemail.com> (raw)
In-Reply-To: <62b0912f0608090822n2d0c44c4uc33b5b1db00e9d33@mail.gmail.com>
On Wednesday 09 August 2006 17:22, Molle Bestefich wrote:
> The hardware works flawlessly.
> The shutdown was a regular shutdown -h.
>
> Messages on the console indicated that Linux actually tried to
> shutdown the filesystem before shutting down Samba, which is just
> plain Real-F......-Stupid. Is there no intelligent ordering of
> shutdown events in Linux at all?
There is no shutdown ordering in the Linux *kernel*, it is
the responsibility of the userspace to arrange for that.
IOW: the distribution packagers should do it,
or you, if you maintain your custom-configured system.
> Samba was serving files to remote computers and had no desire to let
> go of the filesystem while still running. After 5 seconds or so,
Somebody forgot to add a kill -9 to the shutdown scripts.
> Linux just shutdown the MD device with the filesystem still mounted.
>
> That's what happened on a user-visible level, but what could have
> happened internally in the filesystem?
--
vda
next prev parent reply other threads:[~2006-08-10 7:44 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 20:32 ext3 corruption Molle Bestefich
2006-08-08 23:47 ` Molle Bestefich
2006-08-09 1:33 ` Sergio Monteiro Basto
2006-08-09 10:36 ` Molle Bestefich
2006-08-09 11:33 ` linux-os (Dick Johnson)
2006-08-09 15:22 ` Molle Bestefich
2006-08-09 15:38 ` Michael Loftis
2006-08-09 18:28 ` Molle Bestefich
2006-08-09 18:41 ` Mws
2006-08-09 20:17 ` Duane Griffin
2006-08-09 20:47 ` Molle Bestefich
[not found] ` <e9e943910608091527t3b88da7eo837f6adc1e1e6f98@mail.gmail.com>
2006-08-09 23:09 ` Molle Bestefich
2006-08-10 0:08 ` Duane Griffin
2006-08-10 21:00 ` Molle Bestefich
2006-08-12 16:38 ` Theodore Tso
2006-08-12 17:24 ` Molle Bestefich
2006-08-12 21:47 ` Theodore Tso
2006-08-13 19:21 ` Molle Bestefich
2006-08-14 3:23 ` Kyle Moffett
2006-08-14 15:34 ` Theodore Tso
2006-08-14 17:21 ` Molle Bestefich
2006-08-10 3:06 ` Jim Crilly
2006-08-10 9:48 ` Molle Bestefich
2006-08-10 11:41 ` linux-os (Dick Johnson)
2006-08-10 12:21 ` Molle Bestefich
2006-08-10 12:19 ` Helge Hafting
2006-08-10 13:00 ` Molle Bestefich
2006-08-10 14:40 ` gmu 2k6
2006-09-24 8:56 ` Molle Bestefich
2006-09-25 12:27 ` Helge Hafting
2006-10-02 2:40 ` Molle Bestefich
2006-10-02 3:24 ` Gene Heskett
2006-10-02 6:50 ` Kyle Moffett
2006-08-10 16:10 ` John Stoffel
2006-08-10 19:10 ` Molle Bestefich
2006-08-11 8:06 ` Helge Hafting
2006-08-11 13:26 ` Horst H. von Brand
2006-08-12 8:54 ` Molle Bestefich
2006-08-12 10:31 ` Molle Bestefich
2006-08-17 1:27 ` Horst H. von Brand
2006-08-17 13:46 ` Molle Bestefich
2006-08-10 8:32 ` Bernd Petrovitsch
2006-08-10 7:44 ` Denis Vlasenko [this message]
[not found] <Pine.LNX.4.33.0207121337500.8654-100000@coffee.psychology.mcmaster.ca>
2002-07-12 19:05 ` Alec Smith
2002-07-12 20:11 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2002-07-12 15:32 Alec Smith
2002-07-12 15:52 ` Russell King
2002-07-12 19:51 ` Andrew Morton
2002-07-12 16:02 ` Alan Cox
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=200608100944.27396.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=molle.bestefich@gmail.com \
/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