Re: Why can't I flush /dev/ram0?

2001-06-18 Thread Kelledin Tane
> > When I mount the filesystem to check it out, nothing appears to have > > anything open on the filesystem. So why am I not able to flush it > > clean? > > Because of a bug present in Linus tree. Try this patch: Thanks, that seems to have fixed it. There's something else I'm curious about

Re: Why can't I flush /dev/ram0? (fwd)

2001-06-18 Thread Scott Murray
, Ontario e-mail: [EMAIL PROTECTED] -- Forwarded message -- Date: Mon, 18 Jun 2001 23:55:37 +0200 From: Jan Rekorajski <[EMAIL PROTECTED]> To: Kelledin Tane <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: Why can't I flush /dev/ram0? On Mon, 18 Jun 2001, Kelledi

Re: Why can't I flush /dev/ram0?

2001-06-18 Thread Jan Rekorajski
On Mon, 18 Jun 2001, Kelledin Tane wrote: > At this point, I'm trying to get an initrd working properly. So far, it > works, the system boots, etc. etc., but whenever I try to do a "blockdev > --flushbufs /dev/ram0", I get "device or resource busy" > > When I mount the filesystem to check it

Re: Why can't I flush /dev/ram0?

2001-06-18 Thread Kelledin Tane
> If you have a directory called /initrd, in your root file-system, > you may find that the old initrd is still mounted: > > Script started on Mon Jun 18 17:22:20 2001 > # ls /initrd > bin dev etc lib linuxrc sbin > # umount /initrd > # ls /initrd > # exit > exit > Script done on Mon Jun 18

Re: Why can't I flush /dev/ram0?

2001-06-18 Thread Richard B. Johnson
On Mon, 18 Jun 2001, Kelledin Tane wrote: > At this point, I'm trying to get an initrd working properly. So far, it > works, the system boots, etc. etc., but whenever I try to do a "blockdev > --flushbufs /dev/ram0", I get "device or resource busy" > > When I mount the filesystem to check it

Why can't I flush /dev/ram0?

2001-06-18 Thread Kelledin Tane
At this point, I'm trying to get an initrd working properly. So far, it works, the system boots, etc. etc., but whenever I try to do a "blockdev --flushbufs /dev/ram0", I get "device or resource busy" When I mount the filesystem to check it out, nothing appears to have anything open on the

Why can't I flush /dev/ram0?

2001-06-18 Thread Kelledin Tane
At this point, I'm trying to get an initrd working properly. So far, it works, the system boots, etc. etc., but whenever I try to do a blockdev --flushbufs /dev/ram0, I get device or resource busy When I mount the filesystem to check it out, nothing appears to have anything open on the

Re: Why can't I flush /dev/ram0?

2001-06-18 Thread Richard B. Johnson
On Mon, 18 Jun 2001, Kelledin Tane wrote: At this point, I'm trying to get an initrd working properly. So far, it works, the system boots, etc. etc., but whenever I try to do a blockdev --flushbufs /dev/ram0, I get device or resource busy When I mount the filesystem to check it out,

Re: Why can't I flush /dev/ram0?

2001-06-18 Thread Kelledin Tane
If you have a directory called /initrd, in your root file-system, you may find that the old initrd is still mounted: Script started on Mon Jun 18 17:22:20 2001 # ls /initrd bin dev etc lib linuxrc sbin # umount /initrd # ls /initrd # exit exit Script done on Mon Jun 18 17:22:44

Re: Why can't I flush /dev/ram0?

2001-06-18 Thread Jan Rekorajski
On Mon, 18 Jun 2001, Kelledin Tane wrote: At this point, I'm trying to get an initrd working properly. So far, it works, the system boots, etc. etc., but whenever I try to do a "blockdev --flushbufs /dev/ram0", I get "device or resource busy" When I mount the filesystem to check it out,

Re: Why can't I flush /dev/ram0? (fwd)

2001-06-18 Thread Scott Murray
, Ontario e-mail: [EMAIL PROTECTED] -- Forwarded message -- Date: Mon, 18 Jun 2001 23:55:37 +0200 From: Jan Rekorajski [EMAIL PROTECTED] To: Kelledin Tane [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Why can't I flush /dev/ram0? On Mon, 18 Jun 2001, Kelledin Tane wrote

Re: Why can't I flush /dev/ram0?

2001-06-18 Thread Kelledin Tane
When I mount the filesystem to check it out, nothing appears to have anything open on the filesystem. So why am I not able to flush it clean? Because of a bug present in Linus tree. Try this patch: Thanks, that seems to have fixed it. There's something else I'm curious about though...