Skip to contentSkip to conversation

Enhancement of /proc/partitions output (2.5.1-pre5)

PATCH [email protected] 2 participants 2 messages Dec 1, 2001 – Dec 2, 2001

lore
Share & tools
lore
#0 lore raw

From: Anton Altaparmakov <[email protected]>

> It will still break things.

Sure. I anticipated it would break things but then again it is 2.5.1-pre5 and not 2.4.x.

True. But this is the reporting side of the block device stuff. And all is going to be changed. It is better to wait until the new situation has been established.

Quoted 3 lines

Adding such stuff to the kernel would be especially unfortunate if, as I did in my version of the block layer, the unit becomes byte instead of sector. We would have to change again.

So you are going to change it anyway at some point?

Who am I? I have plans, but other people may have other plans, and it is not me who decides.

We could just make the changes at the same time in that case? If it is in bytes even better. Just give start byte and length,

But why not do it in user space?

# ./blockdev --report /dev/hda?
RO    RA   SSZ   BSZ   StartSec     Size    Device
rw     8   512  1024   16450560          2  /dev/hda1
rw     8   512  1024          0          0  /dev/hda2
rw     8   512  1024          0          0  /dev/hda3
rw     8   512  1024         63   16450497  /dev/hda4
rw     8   512  4096   16450623    4096512  /dev/hda5
rw     8   512  4096   20547198   13108977  /dev/hda6
rw     8   512  1024   33656238      80262  /dev/hda7
rw     8   512  1024     481950    4209030  /dev/hda8
rw     8   512  1024      64260     417690  /dev/hda9

(util-linux-2.11n)

And I agree with Andreas the partition type would be useful in the display, too.

I don't.

This type is irrelevant. It would be very bad to make it available. People might start using it, and that can only cause problems. Moreover, usually there is no type, and in the future that I plan there will never be a type. If there is a type, *fdisk will tell you.

[We all have plans, and some of these will actually be implemented. In util-linux I already distribute for quite some time code that will do partition setup. That means that no partition code is required in the kernel. If 2.5 adds an initrd or so to the kernel, so that Linux boots in its own ramdisk, then all partition reading code can be thrown out of the kernel. That is one of my goals. User space comes and tells the kernel: on device /dev/hda, let hda7 be the interval of length 80262 sectors, starting at sector 33656238. It is possible today, but not many people use it. The plan is to make that the only way to get partitions.]

If it really is only a list of available devices why show the size in blocks at all?

History. It happened to be implemented like that. There were some reasons, but not very strong ones.

Andries

#1 lore raw
Quoted 10 lines · At 22:43 01/12/01, [email protected] wrote:

From: Anton Altaparmakov <[email protected]>

> It will still break things.

Sure. I anticipated it would break things but then again it is 2.5.1-pre5 and not 2.4.x.

True. But this is the reporting side of the block device stuff. And all is going to be changed. It is better to wait until the new situation has been established.

That is true.

Quoted 7 lines
Quoted 3 lines

Adding such stuff to the kernel would be especially unfortunate if, as I did in my version of the block layer, the unit becomes byte instead of sector. We would have to change again.

So you are going to change it anyway at some point?

Who am I? I have plans, but other people may have other plans,

Sorry, I meant: s/going/planning/

Quoted 1 line

and it is not me who decides.

True.

btw. You sent a patch to fsdevel some time ago converting parts of the kernel to use bytes instead of 1024 byte blocks. Have you got an updated/more complete version of that?

Quoted 17 lines

We could just make the changes at the same time in that case?
If it is in bytes even better. Just give start byte and length,

But why not do it in user space?

# ./blockdev --report /dev/hda?
RO    RA   SSZ   BSZ   StartSec     Size    Device
rw     8   512  1024   16450560          2  /dev/hda1
rw     8   512  1024          0          0  /dev/hda2
rw     8   512  1024          0          0  /dev/hda3
rw     8   512  1024         63   16450497  /dev/hda4
rw     8   512  4096   16450623    4096512  /dev/hda5
rw     8   512  4096   20547198   13108977  /dev/hda6
rw     8   512  1024   33656238      80262  /dev/hda7
rw     8   512  1024     481950    4209030  /dev/hda8
rw     8   512  1024      64260     417690  /dev/hda9
Quoted 1 line

(util-linux-2.11n)

That's great! Thanks for the info.

Quoted 9 lines

And I agree with Andreas the partition type would be useful
in the display, too.

I don't.

This type is irrelevant. It would be very bad to make it available. People might start using it, and that can only cause problems. Moreover, usually there is no type, and in the future that I plan there will never be a type. If there is a type, *fdisk will tell you.

I am afraid I disagree. - Type is important when a partitioned device is being worked on. LDM for example needs to know the types in order to make sure not to take over a non-dynamic disk by mistake / to know that it is a dynamic disk.

MD RAID uses partition types for autodiscovery of raid partitions during boot.

And there might be other uses... For example IMHO it would make perfect sense to determine which fs to attempt to mount on a partition depending on its type.

Quoted 10 lines

[We all have plans, and some of these will actually be implemented. In util-linux I already distribute for quite some time code that will do partition setup. That means that no partition code is required in the kernel. If 2.5 adds an initrd or so to the kernel, so that Linux boots in its own ramdisk, then all partition reading code can be thrown out of the kernel. That is one of my goals. User space comes and tells the kernel: on device /dev/hda, let hda7 be the interval of length 80262 sectors, starting at sector 33656238. It is possible today, but not many people use it. The plan is to make that the only way to get partitions.]

That sounds cool for normal partitions but how is handling of things like MD RAID and LDM going to be dealt with in that case?

I.e. where several different partitions have to be combined in various ways to give new devices? What are your thoughts on this? And do you have or are you aware of any code for these more advanced uses of partitioned devices?

(I will have a look at util-linux when I have some time.)

Quoted 5 lines

If it really is only a list of available devices why show the size in
blocks at all?

History. It happened to be implemented like that. There were some reasons, but not very strong ones.

The usual answer in other words...

Best regards,

Anton

Signature · 5 lines
  "I've not lost my mind. It's backed up on tape somewhere." - Unknown
-- 
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS Maintainer / WWW: http://linux-ntfs.sf.net/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/