|WikiProject Computing||(Rated C-class, Mid-importance)|
- 1 Merger
- 2 Extended partitions?
- 3 1024 sector limitation
- 4 XOSL link
- 5 Extended/logical partitions
- 6 Hardlink attacks
- 7 Other partitioning implementations
- 8 Too technical
- 9 windows partition setup??
- 10 One technical detail
- 11 Needs more info.
- 12 UNIX partitions??
- 13 Partitioning = Dissection? Not always...
- 14 Active partitions and list of file systems
- 15 Partitions are not limited to hard disks
- 16 "Disk partition" versus "disk partitioning"
- 17 Halve
- 18 Block size
- 19 Overflows and error recovery?
- 20 Depositing error codes?
- 21 Cylinder and volume allocations?
- 22 what is partation
- 23 Benefits
- 24 Rename without "Disk"
- 25 Scope of article?
- 26 lossless resizing?
- 27 dead link lissot.net
- 28 dead link lissot.net
- 29 Not destroying users files when parititions a disk
Hi, I returned the materials moved to Hard disk drive partitioning history, because they don't make up for a whole article. Let me explain: each article in Wikipedia has to reach a balance of size versus integration of details. Now the history of hard drive partitioning is quite integral to the concept of drive partitioning, and it doesn't excessively increase the size. So in this case it's best to leave it in one chunk. Remember, Wikipedia is an encyclopedia with proper articles, not Everything2 with nodes :-) --Uriyan
In fact, the history of partitioning is just about the only thing on the topic. The whole concept of partitioning is completely obsolete. Partitioning (and formatting) make no sense in the case of a Logging FS where you can grow and shrink the log dynamically. -- Ark
- POV, surely -- partitioning is still critically relevant to the vast majority of filesystems. Wikipedia doesn't enjoy the luxury of closing its eyes and pretending that it doesn't exist. --Jkew 19:46, 22 November 2005 (UTC)
To do: Drive partitioning on non- IBM PC architectures was moved from the article to here. --cprompt 02:23, 21 Dec 2003 (UTC)
Extended partition is linked here, but the article doesn't define - or even mention! - extended partitions, let alone explain how they function. Is this missing for a reason, or does it just await writing? --Dyfrgi 22:42, 7 May 2006 (UTC)
- I added a blurb about this when I rewrote the article a bit. Fiskars007 21:19, 10 August 2006 (UTC)
- You can, however, find more details about extended partitions in the article extended_boot_record (EBR). Daniel B. Sedory 05:52, 4 August 2007 (UTC)
1024 sector limitation
The article says:
"Technical limitations of a filesystem or operating system (e.g. old versions of the Microsoft FAT filesystem or old Linux kernels that can't boot on a partition with more than 1024 sectors)"
Is this a reference to the old limitation in LILO that meant it could not boot from a partition that began after the 1024th cylinder on a drive? If so, the statement above needs to be corrected. — Yama 10:00, 15 September 2005 (UTC)
- Linux kernels don't care about details as ranges or sizes. 1024th cylinder limits came because the implementations of LiLO or Grub used BIOS info to boot partitions. --188.8.131.52 (talk) 10:52, 20 June 2011 (UTC)
I have removed the dead link to xosl.org (which now belongs to a link farm):
Although Ranish has a mirror of it, I'm not really sure how relevant an operating system loader is to an article on partitioning -- all the other links are to either further information on partitioning or to partitioning utilities, not to loaders. --Jkew 19:30, 22 November 2005 (UTC)
24 logical partitions in an extended partition? Since when? Assume this is a typo for 4. Should also note that extended partitions can be nested. --Jkew 19:40, 22 November 2005 (UTC)
I think this refers to the limit existing since DOS 3.3 (1987) to have a maximum of 23 logical partitions inside an extended partition (using a chained setup where each partition is preceded by an "EBR" with only two entries, one being the logical, and the other being another extended which points to the next slice.)
The limit of 23 was computed as being 26 (letters) -2 (A: and B: were for floppies) -1 (for C: which had to be primary). --AntoineL 15:16Z, December 5th, 2005
- As AntoineL pointed out, there can be 26 drive letters under DOS/Windows on a PC, so the only typo error was in showing 24 instead of 23, but another OS may be able to create an unlimited number of extended partitions! Linux, e.g., doesn't use drive letters as an IBM/Microsoft OS does.
- Your comment, "Should also note that extended partitions can be nested." is incorrect, at least according to every OS and utility that I've tested. None of them ever created a nested extended partition! See the discussion page for extended boot record. If you know of a utility/OS that truly creates nested partitions, please list all the details there. Daniel B. Sedory 18:07, 4 August 2007 (UTC)
Would be useful to provide a link to this for those (like me) who had their interest piqued -- can't find anything suitable within Wikipedia. --Jkew 19:49, 22 November 2005 (UTC)
- Google. ;^ ] 184.108.40.206 22:45, 26 January 2006 (UTC)
Other partitioning implementations
Concurrent schemes used
There are a number of them; GNU Parted or Linux fdisk support a few like the Unix-inherited (BSD, Sun, etc.) disklabels or the Apple Macintosh scheme; there is also the SCO Xenix divvy scheme which may be historically relevant.--AntoineL 15:51Z, December 5th, 2005
Intel GUID Partition Table
A recent edit (Nov 30th) added
Its however unlikely this project will ever replace IBM PC partitions as the Itanium processor was not received well by the market.
While factually correct about Itanic, I do not agree with the conclusion. For the PC architecture, GPT is still the only scheme with some acceptance which saves the 2TB barrier (32-bit count of 512-byte sectors). It is implemented in Linux, BSD, and the recent versions of Windows.
I am not to say GPT will be the solution (would be a POV.) Booting is certainly still a problem to solve, and the BIOS makers are expected here; also AMD does not seem willingful to acceptance the EFI standard as a whole (but GPT can easilly be severed.)--AntoineL 15:51Z, December 5th, 2005
In reading this article, I have come across quite a few terms that would definitely not be readily identifiable to many people who use PCs. Jargon terms are used rather than simple English- defining/wikifying the terms would be a good idea. On the whole, the article is well written from a basic techie viewpoint, but that moves it away from being generally useful to a broad base of Wikipedia readers.
- I agree with you - i actually did try a bit at fixing that up a bit. I find it less confusing now, but it's also noticeably shorter (mostly because the List of partition utilities was given it's own article). Fiskars007 21:19, 10 August 2006 (UTC)
I was about to try and fix a bit as well, but the oversimplistic Linux-centric view is very unhelpful, and AFAICT, inaccurate, especially all the stuff about how things are partitioned, it would be nice to see Slice vs Partition explanations and where it starts talking about LVM's perhaps a good example as provided by HP (not the Linux copies) would be more helpful than just this stuff about how Linux does it this way or that way. Most people don't use Linux. -- Steve Roome --220.127.116.11 23:53, 1 May 2007 (UTC)
- We already have a slice (disk) article, and BSD disklabel; would a merge make sense? Note that partitions are used by DOS and NT-based systems as well as Linux. –EdC 22:05, 2 May 2007 (UTC)
- We no longer have a slice (disk) article; we have a slice (disk) redirect to this article, with the article now mentioning that "slice" is a term used for disk partitions in Solaris and FreeBSD. Should BSD disklabel be merged here as well? Or should it be left separate, as it's a particular mechanism used to partition disks, just like the MBR mechanism? Guy Harris (talk) 20:27, 22 March 2013 (UTC)
windows partition setup??
talking about windows partitions... should the programs and files (eg my docs) be stored together on a 2nd partition, or both separately on a 2nd and 3rd?? - mar 1st —The preceding unsigned comment was added by 18.104.22.168 (talk • contribs) 18:20, 1 March 2006 (UTC)
- You should put this sort of question on a computer tech support forum or similar where it may be better answered - this is an encyclopedia, not an IT help desk. If you'd like my recommendation, you would be able to get by with just one or two partitions - adding more partitions makes your life harder, and you run the risk of running out of space for example documents while you still have room for programs (like what often happens to users on Unix-like operating systems). Fiskars007 21:19, 10 August 2006 (UTC)
One technical detail
The drive mentions making the C drive "nonexistent" and putting the OS on another drive. Could this somehow be clarified? —The preceding unsigned comment was added by 22.214.171.124 (talk • contribs) 00:04, 24 March 2006 (UTC)
- No idea how that works. My computer actually boots Windows XP from H:, not C:, but I still have a C: drive. I think that it's a requirement in Windows still that you must have a C: partition, a holdover from MS-DOS... but I really have no clue. Research should be done on this, or it should be removed. 126.96.36.199 20:48, 10 August 2006 (UTC)
- Often, to create extra space, a hard disk is compressed. When this happens, the compressed data is basically stored as one huge file on the hard disk. It is then opened and treated as a separate disk. To avoid confusion, the drive letters are often swapped, so that the compressed data is C: and the original hard disk (containing the compressed file and usually all or part of the system) is given another letter.188.8.131.52 16:06, 28 October 2006 (UTC)
Needs more info.
On Primary, Logical and Extended Partitions. BKmetic 14:29, 17 May 2006 (UTC)
- I added a mention of them - they should be expanded. I will mark it as a stub. Fiskars007 21:19, 10 August 2006 (UTC)
According to the article /boot is its own partition. That makes no sense, /boot includes files that is needed to define how to mount the partitions defined in /etc. For these reasons, /boot, /etc, /proc and /bin cannot be their own partitions or the system won't boot. Better be correct. And also, note that very few distributions actually make that making partitions by default. --[Svippong - Talk] 20:49, 23 November 2006 (UTC)
- What you said here is incorrect: I've been booting up my Linux systems for years with a SEPARATE
/bootPARTITION. My /boot partition, as do all of them, contains a copy of the Linux kernel, which knows full well how to access whatever data it needs before booting up the whole system completely. You are correct that many recent distributions default to just dumping everything in a single '/' partition, but even under some Live CDs, with some planning, it's possible to install them to more than one partition. Daniel B. Sedory 10:28, 12 April 2007 (UTC)
Partitioning = Dissection? Not always...
"In layman's terms, partitioning a hard drive makes it appear to be more than one hard drive, especially in how each partition is formatted for different operating systems, and in how files are copied from one partition to another."
Not true. Partitioning is not JUST subdividing a physical hard drive into multiple logical partitions, even creating one partition on one hard drive is still partitioning, just not as advanced. Also, partitioning several disks (such as disks in a RAID format) still do not involve taking one hard drive and dissecting it.
Basically, since I can't think of how to reword it, someone else think of it. (This is in the intro)
--DEMONIIIK 01:13, 9 April 2007 (UTC)
- How about one of these:
- Partitioning a hard disk reserves some specific area within it so that an operating system may use that space as a whole logical drive or as part of a larger file system. A single hard disk may thus contain one or more logical drives or even just part of a logical drive that could span several hard disks.
- Partitioning a hard disk defines specific areas (partitions) within the disk so that they may be used by one or more Operating Systems. Any one partition may form part of a larger file system or it may be an entire logical drive.
- Partitioning a hard disk drive defines specific areas (the partitions) within the disk. A partition may constitute an entire logical drive or it may form part of a larger logical drive which could span over several partitions and hard disks.
- Intersofia 15:31, 22 May 2007 (UTC)
Active partitions and list of file systems
- It appears that trying to squeeze gigs of data into a CDROM will give rise to an active partition, up until the CDROM becomes full, after which the partition probably becomes inactive.
- As for a list of file systems, that would be outside the scope of this article's main page. Best to click your mouse on the link for file systems, and ask over there. Dexter Nextnumber (talk) 01:16, 5 January 2010 (UTC)
Partitions are not limited to hard disks
Correct me if I am wrong, which is why I haven't waded in to correct the article. A partition is a way of dividing up space in a volume. A Volume can be anything from a file on a filesystem already present to a real hard disks volume, in some situations a volume can span a number of hard disks or other storage media. So as I see it the hierarchy is a follows:
Physical Storage media
>>Partition Table (or system specific equivalent)
- It's more complicated than that (of course!). There are various ways of slicing and dicing disks, and partitioning is only one of them. You basically do one of of two things:
- Join volumes together (either to make more space, or more redundancy):
- Mirroring (RAID 1)
- Striping (RAID 0)
- RAID 5
- Disk concatenation
- Logical volume groups
- Divide a volume into pieces (for ease of administration)
- Disk partitioning
- Logical volumes
- Join volumes together (either to make more space, or more redundancy):
- So you might do something like this with 4 100GB disks:
- Partition disks up into 4*50GB and 2*100GB
- Mirror equal sized partitions to get 2*50GB mirrors and 1*100GB mirror
- Make a volume group out of 1*50GB mirror and 1*100GB mirror to give you a 150GB volume group
- Divide the volume group into 2*75GB logical volumes
- Use the 50GB mirror and 2*75GB logical volumes as you want
- I haven't even mentioned hardware RAID, SANs etc. The disks mentioned in step 1 could actually be made of multiple disks striped together in hardware (Do NOT do this! Mirror first, then stripe), or be network SAN volumes that have themselves been sliced and diced from a pool of hundreds of disks. Storage management is getting more and more abstract, with more and more layers. What is a "physical disk" in one layer is just a "logical volume" in the layer below.184.108.40.206 (talk) 17:15, 30 March 2009 (UTC)
So the common usage of partitioning the hard disk is not strictly true.
And the term Volume comes directly from the literal meaning for space.
Interestingly on some systems, (GNU/Linux) included, one can write a filesystem directly to a block device and skip the partitioning altogether, a filesystem directly on a volume. In this case one does not, for example, mount "/dev/hda1" but the equivalent would be "/dev/hda".
With all of the references to hard-disks in this article it is a big edit and one that I would appreciate some feedback on beforehand.
- User 220.127.116.11, actually, it depends upon the system used to do the partitioning! Under any DOS OS or even many UNIX/Linux 'fdisk' programs, or anything that Microsoft now refers to as "Basic Disks," some of your comments above would definitely be in error.
- But before I go into that, let me say I'm glad you brought this up, since most servers no longer use simple "Basic Disk" configurations, and there should be an article which addresses what is commonly found on such systems! However, the present article has always (so far at least) reflected "Disk partitioning" on Basic Disks only. We need to ask some very experienced AND computer savvy Wikipedia editors if they believe the topic should be covered under different articles (maybe such articles already exist!), or if the present article should be altered to include both "Basic" and what Microsoft calls "Dynamic Disks."
- As to your comment: "A partition is a way of dividing up space in a volume." That is incorrect! The term "volume" or "logical volume" (at least under "Basic Disks"), is either equivalent in size to a partition or smaller than a partition, but you never divide a volume into partitions. A primary NTFS partition (on a "Basic Disk") will always be one sector larger than the Volume it contains. It is not the Volume boot record sector, but rather a 'backup' boot sector that it stores in the last sector of the partition. And all extended partitions, of which there should be only one per disk, will contain one or more "logical drive volumes" within it.
- When we move to "Dynamic Disk" schemes, a logical volume can 'span' across more than one physical hard disk! Will discuss this further at a later date. Daniel B. Sedory (talk) 22:11, 11 February 2008 (UTC)
I have just a few minutes to add a bit more: You can define any word however you want, but that won't change how it's already being used by computer industry leaders, techs, journals, etc. This made me search Wikipedia for its use, and I found the article: Volume_(computing). It does point out that volumes can exist without partitions and that volumes can span physical disks, etc., but begins by describing a volume as: "a single accessible storage area with a single file system, typically (though not necessarily) resident on a single partition of a hard disk."
As to your comment, "one can write a 'filesystem' directly to a block device and skip the partitioning altogether," is this really any different than writing a raw image file to a floppy or hard disk drive under a Windows OS?! Unless you meant something entirely different, the 'file system' you speak of would still have to be formatted or even partitioned first and then formatted before being written to the disk. Perhaps you meant how some devices, such as a USB stick, etc. can easily be set up as a single volume (no MBR sector)? But these too could also be partitioned if I wanted them to be (except for using a diskette in a real floppy drive). The main point in all of this is that partitions are never within a volume, but the opposite is quite often true! Daniel B. Sedory (talk) 10:54, 13 February 2008 (UTC)
- To me, «write a filesystem directly to a block device» is unmistakable — he literally means formatting the block device. I am using a harddisk formatted this way right now!
- Example: Let /dev/sdx be a harddisk (of the type BIOSes expect to find a partition table on).
- Then, noone stops you from doing `mkfs.ext4 /dev/sdx && mount -t ext4 /dev/sdx /mnt/MyEntireHarddisk`.
- Pros/Cons: You won't be able to boot from a harddisk formatted this way, and partitioning tools will mistakenly assume that unformatted==unused space, but the zero filesystem offset satisfies every thinkable alignment (ideal for SSDs).
- Let's define "volume" as where you can put a filesystem:
- Anordal (talk) 00:15, 13 February 2013 (UTC)
"Disk partition" versus "disk partitioning"
WP:VERB says "do not use verbs for article titles if there is a more appropriate noun title". It's true that, when initially creating partitions, one describes it as "partitioning the drive". However, discussion and documentation seems to use the noun form much more frequently... primary partition, partition table, swap partition, etc. In my opinion, the article should be renamed to "disk partition". --Underpants (talk) 04:27, 14 June 2008 (UTC)
- Both words, "partition" and "partitioning", can be nouns or verbs, depending on their use in a sentence. Since an article title isn't a sentence, there's no way to determine which part of speech is intended. Giving Wikipedia the benefit of the doubt, I'd consider them both nouns when used as titles of articles, so WP:VERB doesn't apply. Unfree (talk) 17:31, 13 August 2009 (UTC)
From the article: "This partition is expected to: occupy the outer tracks of the hard drive, more than double the throughput, more than half the access time."
I suspect the editor intended to say "more than halve". I'd change that, considering that more than half isn't as good as less than half, which was probably intended, but what about the verb-noun confusion? Unfree (talk) 17:20, 13 August 2009 (UTC)
Overflows and error recovery?
I tried to read the main page to this article and remain confused.
There are lots of file systems that support the concept of a "partition" but the main article seems to proceed on the theory that the user is using (and is familiar with) PC compatible harddrives, on which many partitions may be found. But I am not a PC user, and don't understand how PC harddrives work. I have only theory to fall back on, and since I don't have a PC compatible, I find their method of solving the overflow problem to be less than interesting. In fact, most of the article on that account could be deleted because it is not particularly notable to those who do not own PCs.
How does a typical file system usually deal with an overflow condition? Does the partition automatically expand, as by automatically editing itself, and thus getting bigger? Or does the file system automatically create a new partition, and deposit the overflow there? Dexter Nextnumber (talk) 06:33, 4 January 2010 (UTC)
- Typically, nothing happens when a filesystem becomes full. Resizing and creating new partitions or filesystems is usually a manual intervention. Letdorf (talk) 17:52, 4 January 2010 (UTC).
Depositing error codes?
Is there a way of determining which partitions receive file read/write errors? And if there are, which partition receives the error codes? Or errors relating to misused channels? Is this sorted in any way? Is there at least one file system that automatically creates new partitions when old partitions are full, or when they approach a near-critical density? Dexter Nextnumber (talk) 06:39, 4 January 2010 (UTC)
Cylinder and volume allocations?
For those of us who are much more familiar with BAMs than FATs, how many file systems define their partitions in terms of allocated cylinders and volumes? I can't be the only one who thinks the FAT system is way too clumsy to be of any practical use. Dexter Nextnumber (talk) 00:49, 5 January 2010 (UTC)
what is partation
"Having an area for operating system virtual memory swapping/paging." I'm not saying this is wrong, but is this an actual benefit? Just about every disk, even one with a single partition, already has such an area. If the disk is partitioned, then the page file will be limited to one partition. One theoretical advantage is that the read/write heads will not have as far to travel, as mentioned under "Short stroking". On the other hand, the page file may become fragmented, forfeiting some of those advantages.
- What this statement is referring to is a swap partition, ie. a raw partition (without a filesystem on it) used entirely for swap space. Older UNIX and UNIX-like OSs didn't support swap files, so swap partitions were the only option. For systems that support both, in theory, a swap partition should be faster, as pages are read and written directly from/to the disk device, without the overhead of filesystem I/O. In addition, some UNIX systems can use a swap partition for temporary storage of system crash dumps in the event of a kernel panic. See, for instance . Letdorf (talk) 21:41, 11 May 2010 (UTC).
Rename without "Disk"
Since this applies to general secondary storage (e.g., SSDs, etc.) and not just disks (e.g., HDDs), I propose renaming the article to not contain the word "disk". Perhaps there are better ideas but my initial choice is "Drive partitioning". Uzume (talk) 16:09, 23 May 2010 (UTC)
- Nomenclature is tricky here. While SSDs contain no circular components, and hence are not "disks", they also contain no moving parts, and hence are not, strictly speaking, "drives" either. To be pedantic, this article should probably be called "Secondary data storage device partitioning", but I think that might be going too far! --Letdorf (talk) 12:00, 24 May 2010 (UTC)
- IBM faced this issue in the 1960's, and coined the term DASD as a generic term for referring to data cells, disks and drums. Why not use that here? Shmuel (Seymour J.) Metz Username:Chatul (talk) 15:16, 31 December 2010 (UTC)
- "Secondary data storage device partitioning" would go too far indeed :-). I would go for "Drive partitioning", although strictly speaking not correct. But you cannot just rename the article, because some details are only about HDD and not about SSD or USB or ... Eg. I don't know if an SSD also works with an MBR? --Mattias.Campe (talk) 14:19, 19 January 2014 (UTC)
- I don't think you partition tape drives, optical drives or floppy disk drives so "Drive partitioning" seems out. I'm not sure u can partition a USB thumb drive either. Since SSDs generally present themselves to the system as an HDD I suggest we leave the title alone and deal with SSDs with a footnote if at all. After all in Windows SSD partitioning is under Disk Management. Tom94022 (talk) 07:00, 20 January 2014 (UTC)
- "I'm not sure u can partition a USB drive either." You can - I just did. (I didn't really need that ancient Quicken backup anyway. :-)) 4 partitions. And we're talking "USB drive" in the sense of "USB thumb drive", not "USB-attached HDD", which I'm certain you can partition - the OS, or, at least, most if not all OSes, don't care. USB-attached drives, like Firewire-attached drives and Thunderbolt-attached drives, present themselves to the system, except maybe at the lowest layer, the same way HDDs do; whether I'd call that "as an HDD" is another matter. Guy Harris (talk) 07:19, 20 January 2014 (UTC)
- Thanks for the clarification. To be even more clear, as I understood it when I wrote the above, USB thumb drives cannot be partitioned under the Microsoft supplied Windows OS since the drive is identified as removable media; however if the removable bit is changed so that the drive is recognized as non-removable media then it can be partitioned like any normal hard disk drive. What I was not certain about was whether there were ways other than this hack to do so, particularly in OSes other than Windows. I'm still not sure :-) But that really doesn't matter since even if USB thumb drives can be partitioned by some means that doesn't mean all drives can be - can a "Firewire-attached [tape] drive" be partitioned? Therefore the proposed title change remains IMO inappropriate. Tom94022 (talk) 17:12, 20 January 2014 (UTC)
- The means I used to partition the thumb drive was Disk Utility, the same app you use to partition any other disk on OS X, so, yes, you are now sure that there are ways other than a hack to partition USB thumb drives - or other any other drive externally attached via USB/Firewire/Thunderbolt/etc. - like other drives on at least one operating system.
- The key technical difference isn't whether it's called a disk or not, the key technical difference is whether it's a random-access device or not. If somebody built, for example, a USB DECtape controller offering a random-access-device interface, and plugged it into a box running OS X (or, I suspect, at least some other non-Windows personal computer operating systems), you'd be able to partition it if it had enough blocks to be partitioned and formatted on that OS. Unfortunately, I'm not sure there's a good term to use other than "disk" for that; as noted above, the IBM mainframe term "Direct Access Storage Device" is "not widely used outside that context", so calling the page "DASD partitioning" would probably confuse most readers. If somebody can suggest a term that would be understood by most people and that covers random-access devices regardless of whether they have spinning disks coated with magnetic material or not (and whether or not they're attached via an "external" bus or not), that would be great. (I'm not sure about "drive" either, for no other reason that, for drives with removable media, you're partitioning the medium, not the device into which you insert the medium.) Guy Harris (talk) 19:40, 20 January 2014 (UTC)
- Thanks for the info about OSX. FWIW, I don't think partitioning is necessarily limited to random access; one could partition a tape medium - but I don't know of any OS that does. Since OSX uses "Disk Utility" to partition USB Thumb drives can we now agree that the article title does not need to be changed? Tom94022 (talk) 07:36, 21 January 2014 (UTC)
Scope of article?
The current text of the article discusses partitioning of disks on a PC, where the partioning information is carried on the disk itself. Is partitioning software where the data structures are external to the disk in scope, e.g., minidisks in CP-67 and VM? Shmuel (Seymour J.) Metz Username:Chatul (talk) 15:16, 31 December 2010 (UTC)
- Yes, I'd say partitioning systems where there is no on-disk partition table should be included, if reliable sources can be cited. Regards, Letdorf (talk) 22:17, 3 January 2011 (UTC).
I'm just wondering that there is virtually no Software known that declares to lossles resize partitions. For now i only see FIPS and ntfsresize. (Both with quite limited scope) --Itu (talk) 00:52, 9 January 2012 (UTC)
Not destroying users files when parititions a disk
This article can be improved. I have C drive. However, I want to split this into two. However, I want to preserve the file data. I think a program like Partition Magic, seem to be able to create a partition without loosing data. However, there are a lot of programs out there, which do not preserve existing data on the disk.
can there be additional information about programs which preserve user files versus programs which do not?
- Wikipedia is not a manual, guidebook, textbook, or scientific journal. There could be such information, but relying on Wikipedia as the place to get such information is unwise. Guy Harris (talk) 21:38, 8 April 2014 (UTC)