Hi Roderich,
On Fri, 08 Dec 2000, Roderich Schupp wrote:
>> And I'll ask again... If this is now the recommend mount point,
>> can we have devfs create this directory for us?
>
> C'mon guys, this is just to easy:
Included in 2.4.0-test13-pre3...
Greetings
Christoph
-
To unsub
Chris Meadors wrote:
>
> On 6 Dec 2000, H. Peter Anvin wrote:
>
> >
> > Please don't use the path /var/shm... it was a really bad precedent
> > set when someone suggested it. Use /dev/shm.
> >
>
> And I'll ask again... If this is now the recommend mount point, can we
> have devfs create this d
Chris Meadors wrote:
>
> On 6 Dec 2000, H. Peter Anvin wrote:
>
> >
> > Please don't use the path /var/shm... it was a really bad precedent
> > set when someone suggested it. Use /dev/shm.
> >
>
> And I'll ask again... If this is now the recommend mount point, can we
> have devfs create thi
On 6 Dec 2000, H. Peter Anvin wrote:
>
> Please don't use the path /var/shm... it was a really bad precedent
> set when someone suggested it. Use /dev/shm.
>
And I'll ask again... If this is now the recommend mount point, can we
have devfs create this directory for us?
-Chris
--
Two pengui
Followup to: <[EMAIL PROTECTED]>
By author:Andre Hedrick <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Did you set and mount a "/var/shm" point?
>
Please don't use the path /var/shm... it was a really bad precedent
set when someone suggested it. Use /dev/shm.
-hpa
--
Did you set and mount a "/var/shm" point?
On Wed, 6 Dec 2000, Udo A. Steinberg wrote:
> Hi,
>
> Andre Hedrick wrote:
> >
> > No way that this could cause corruption it is a read-only test.
>
> As others pointed out, it's probably something related to shared
> memory, but it's definitely hdp
Hi,
Andre Hedrick wrote:
>
> No way that this could cause corruption it is a read-only test.
As others pointed out, it's probably something related to shared
memory, but it's definitely hdparm that triggers it. I haven't
got the hdparm sources here to look at what exactly it's doing,
but there
On Wed, Dec 06, 2000 at 11:41:51AM -0800, Andre Hedrick wrote:
> No way that this could cause corruption it is a read-only test.
It definitely does, I saw it, too. It seems to be triggered
by invalidate_buffers().
Jan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
No way that this could cause corruption it is a read-only test.
On Wed, 6 Dec 2000, Udo A. Steinberg wrote:
>
> Hi,
>
> Following the discussion in another thread where someone
> reported fs corruption when enabling DMA with hdparm, I've
> played around with hdparm and found that even the rat
On Wed, 6 Dec 2000, Udo A. Steinberg wrote:
> Hi,
>
> Following the discussion in another thread where someone
> reported fs corruption when enabling DMA with hdparm, I've
> played around with hdparm and found that even the rather
> harmless hdparm operations are capable of trashing an ext2
> fi
On Wed, Dec 06, 2000 at 06:25:15PM +0100, Udo A. Steinberg wrote:
> hdparm -tT /dev/hdb1 does the trick here.
>
> After that, several files are corrupted, such as /etc/mtab.
> Reboot+fsck fixes the problem, however e2fsck never finds
> any errors in the fs on disk.
I'm currently trying to isolat
Hi,
Following the discussion in another thread where someone
reported fs corruption when enabling DMA with hdparm, I've
played around with hdparm and found that even the rather
harmless hdparm operations are capable of trashing an ext2
filesystem quite nicely.
hdparm version is 3.9
hdparm -tT
12 matches
Mail list logo
