It happens on UP as well, I've been reporting this bug with several emails a
day nailing it down since last thursday, haven't gotten anywhere. I finally
determined why processes were going into D state yesterday.
I've had three responses, one confirming it wasn't the new SHM fs, one
recommending SGI's kdb, and one recommending Ingo's ikd.
Anyways. It's broke for all builds as far back as at least 2.3.36, possibly
further.
-d
On Wed, 22 Mar 2000, H. Peter Anvin wrote:
> Date: Wed, 22 Mar 2000 14:46:52 -0800 (PST)
> From: H. Peter Anvin <hpa@transmeta.com>
> To: linux-kernel@vger.rutgers.edu
> Cc: tytso@valinux.com
> Subject: Loopback driver in 2.3.99-3.6
>
> Hi all,
>
> I presume this is already well known, but using the loopback device on
> 2.3.99-3.6 (SMP kernel on SMP machine) causes fatal filesystem cache
> corruption. Sooner or later the process using it will end up in D state,
> and a lot of other processes will too at some point, even if they are not
> using the loopback-mounted filesystem.
>
> The filesystem I was using was iso9660, mounted ro.
>
> -hpa
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Mar 23 2000 - 21:00:37 EST