[lkml]   [2001]   [Nov]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] Ramdisk ioctl bug fix, kernel 2.4.14

Alan Cox wrote:

>>Most disk devices can't change their size with a few commands as a ram disk can
>>as it's a physical constant. Ram disks are virtual so their size is whatever
>>the user specifies, with a kernel configured upper limit. I argue that the size
>>is the allocated amount, not the upper limit.
> I think your problem is that you are querying the disk to ask it the file
> system size ? If so you asked the wrong code

I take your point. The file system knows its right size. However, it would
still be useful to be able to tell what the ram disk allocated size actually is.
Currently there's no good mechanism I know of that returns the actual
allocated size.

I'm using ram disks as a way of building a single floppy linux I'm working on (a
variation on LRP and Tom's Root Boot). Some of the time in this process I have
ram disk(s) without filesystems to query for the size. It's also possible to
build a filesystem that's smaller than the allocated size.

Mypatch doesn't affect userland tools like "du" and "df" since they query the
filesystem for the size. It does fix lowel-level tools that look at the ramdisk
and not the filesystem.

Having the ramdisk report the max possible size and not the allocated size is
akin to having a physical hard disk report the theoretical max that could be
achieved using current technology, not the actual blocks the device is built to


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:13    [W:0.049 / U:2.160 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site