|WikiProject Computing||(Rated C-class)|
The main page of this article lacks a description of volumes used in non-FAT file systems.
ECMA 167's defintion of a logical volume
According to sections 5.6, 5.7 of part 3 of ECMA-167 (which is the framework for the UDF standard used in removable media such as DVDs,Blue-ray discs, etc.)
A Logical Volume is defined as: A logical volume is a non-empty set of partitions.
A Partition is : An extent of logical sectors within a volume. (An extent means a set of contiguous sectors)
The above definition for logical volume seems quite different from the one mentioned in this article.Of course, the definition might be only within the scope of the ECMA-167 and UDF documents, but these are major standards, and may still be a cause for confusion. (It certainly caused me confusion,because my idea of what a Volume is, was based on this Wikipedia article)
On an IBM Series/1, under the EDX operating system, the name "volume" referred to a concept which was quite similar to a partition in that it was of fixed size and could not have any sub-volumes (except on floppy disks), and was used as a directory with a fixed number of entries. A "partition", however, was the name given to a segment of the main storage (RAM). --Jost Riedel (talk) 15:15, 1 September 2010 (UTC)
what is a boot volume
what exactly is a "boot volume"?
the term "boot volume" is used in the article, but it is not defined. -- 15:19, 12 November 2011 184.108.40.206
- One which contains bootstrapping code to start a computet. AnonMoos (talk) 03:48, 15 August 2012 (UTC)
Proposed merge with Volume (compression)
- Please merge it, tbh this article isn't great. It has no citations and its a stub. It would be better to merge with Volume (computing) and create a redirect. Thanks, George (My Talk Page) 17:37, 1 January 2014 (UTC)
- Do not merge this article, I don't know why this was even suggested the two do not have anything to with each other. I think you need to re-read the articles Senator2029 aside from the names they don't have any relevance to each other. their not the same thing and DO NOT belong together--Nerdbits (talk) 02:12, 26 August 2014 (UTC)
- In it's current state Volume (compression) could very well be integrated. The problem is, that the Volume (compression) article is not very detailed, to use an understatement. I believe there is more to say about oompressed volumes, across the different OSes and Filesystems (ZFS to name one). To state that they have don't have any relevance to each other is quit bold. Of course when reading about volumes one wants to read about compressed volumes as well. 220.127.116.11 (talk) 10:46, 5 April 2015 (UTC)
- It sounds like we're at the #4 "contradiction" level of Graham's Hierarchy of Disagreement (part of the WP:AADD essay), with one saying it is relevant and the other saying it is not relevant. Honestly, that's much better than what passes for "discussion" at many other places on the internet, so bravo all around.
- Nevertheless, I think we can kick it up a notch to #3, #2, or #1 sections of the hierarchy.
- I'll begin: I hear that so-called "whole-disk compression" and Category:Compression file systems never actually applies to an entire hard disk -- when a hard disk has several partitions, the whole-disk compression utility handles the data in each volume independently -- sometimes each volume is managed by a different and completely incompatible "whole-disk compression utility". So perhaps it might be more accurate to call it "whole-volume compression". I agree with Georgeh109, Senator2029, etc. that such whole-volume compression is closely related to the kind of thing discussed in this volume (computing) article.
- Often people want to back up a large set of data that is too big to fit on a single disk of storage media (floppy disks or compact disks or DVDs or emails with limited-size attachments or etc.). So they create a so-called "split Zip file", which is technically not a single file, but a series of files, each file (just barely) small enough to fit on a single disk. Typically the split Zip file for one set of data is a series of numbered files (volumes) that all have the same names, but unique extensions ".z01", ".z02", ".z03", ... ".zip". Confusingly, each of those files is called a "volume", and apparently the volume (compression) article discusses this kind of volume, which I agree with Nerdbits is very different from the kind of thing discussed in this volume (computing) article.
- --DavidCary (talk) 16:28, 23 July 2015 (UTC)
"Mount points have been left at defaults." What does that mean in regard to the following table ? There´s no column header, that says "mount point."
The origin of volumes
Volumes go back at least to OS/360 in the early 1960's, if not earlier. The article makes it seem that they started with MS-DOS, or some similar system. For OS/360, volumes can be either tape or disk. Even more interesting, OS/360 allows for multi-volume data sets, especially on tape, though also removable disks. This feature, and tape volumes, do not seem to have survived into MS-DOS or Windows. Note that OS/360 volumes continue through MVS and z/OS. Gah4 (talk) 21:51, 29 July 2015 (UTC)