[lkml]   [2001]   [Mar]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Ramdisk (and other) problems with 2.4.2
On Wed, 7 Mar 2001, Richard B. Johnson wrote:

> On Wed, 7 Mar 2001, Mike Galbraith wrote:
> > I'd sweat bullets over system integrity if _I_ got this reply ;-)
> > Something is seriously amiss.
> Well now the denial phase sets in. This system has run fine for
> two years. It ran until I tried to use new kernels.

?? It's not denial Richard. I showed you your script running here and
working just fine. As to your system running fine for two years, all
I can say is that _every_ system runs fine until it doesn't any more.

There may be a problem elsewhere, but the ramdisk does not display
the symptom you claimed it would.

> Question. How come you show a lost+found directory in the ramdisk??
> mke2fs version 1.19 doesn't create one on a ram disk.

Well it certainly does create a lost+found here as you can see. It
sounds as though you're implying that I dummied up the script output.

> Script started on Wed Mar 7 12:22:20 2001
> # mke2fs -Fq /dev/ram0 1440
> mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
> # mount /dev/ram0 /mnt
> # ls -la /mnt
> total 0
> # umount /mnt
> # exit
> exit
> Script done on Wed Mar 7 12:23:21 2001
> Also, check your logs. The errors reported don't go out to stderr.
> They go to whatever you have set up for kernel errors.

I know what kernel messages are. There are none.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:29    [W:0.096 / U:10.788 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site