|
From: Szakacsits S. <sz...@si...> - 2004-05-06 10:07:32
|
On Wed, 5 May 2004, Dave Pacheco wrote: > I apologize if this is a common question, but I could not quite find the > answer in the documentation. No, it's not common and I'm sorry but I can't tell what's the problem if you don't send the 'ntfsresize --info partition' output. The known limitations are documented in the ntfsresize manual page: There are some very rarely met limitations at present: filesystems hav- ing bad sectors, highly fragmented Master File Table (MFT), relocation of the first MFT extent and resizing in the middle of some metadata in some cases aren't supported yet. These cases are detected and resizing is refused, restricted to a safe size or the closest safe size is dis- played. Note, XP can defragment the MFT so in theory you can't have the above highly fragmented MFT problem. > I am using ntfsresize through qtparted[1] using the latest > SystemRescueCD (www.sysreccd.org), which claims to have ntfsprogs 1.9.0. ntfsresize from command line prints the version. > When trying to resize, it was first reported that I could only free up > about 1-2 MB. But clearly, there should be at least several GB of free > space available. If I read the documentation correctly, this version of > ntfsresize should be able to shrink the filesystem, even without > defragmenting first. However, just to check, I tried defragmenting the > drive with the Windows XP defragger. Ntfsresize was then able to free up > 90MB. This is still not nearly enough for my purposes (installing a > Debian system). It sounds you don't have the latest systemrescuecd ... > Is this a known issue? Is there any known workaround? Or am I doing > something completely wrong...? Any help would be appreciated. Thanks in > advance. Pretty lot of people uses it day by day without any problems. Yours would be the first such complain since release of version 1.9. Cheers, Szaka |
