|
From: Jim K. <jek...@kl...> - 2003-08-01 15:10:28
|
Szaka - Many thanks for your responses! Szakacsits Szabolcs wrote: > Hi Jim, > > On Thu, 31 Jul 2003, Jim Kleckner wrote: > Partimage NTFS support is experimental, for very very long time. I checked > out its NTFS code and I wouldn't trust it 100%. But the most cases it > should work. This was one of the many reasons I wrote ntfsclone that is > very similar to g4u in functionality (I think, I didn't have time to check > it out) but it is optimised for NTFS, so it's much faster. However it also > doesn't support bad sectors but it would be easy to add ... ntfsclone sounds very useful. Hopefully it can also use a simple network connection like g4u. Suceeding in the presence of a few bad sectors would be useful. Disks often give you some "warning" before they go completely bad by starting to gradually get more bad sectors. >>stymied because ntfsresize refuses to operate on a filesystem >>with a non-empty bad cluster file. However, now that it is a >>fresh drive, the bad sectors are now just zero-filled and not >>bad any more. So what I want to do is just remove the bad >>cluster file. Any suggestions? > chkdsk /r /f doesn't do it? We have all code that's needed to do this but > they aren't put together into ntfsck. I ran chkdsk /r /f overnight and ntfsresize still gave up because of the presence of the $BadClus file. Interestingly, I used ntfsinfo to display inode 8 and it indicated that there were no allocated blocks, suggesting that chkdsk may have returned them to service. Unfortunately, I didn't inspect this prior to running chkdsk so I don't know if this is a correct inference. If it is, then perhaps the ntfsresize test could be softened to check for the size? I haven't studied the details as you have so maybe there is some other way this is recorded. >>Does anyone know a good way to do this? I will also try a >>chkdsk /r /f overnight on the off chance (unlikely) that it will >>re-scan the bad blocks. The web would have mentioned it if it >>did. > Please let us know. See above. It may have worked but ntfsresize didn't. >>To my chagrin ntfsresize detected the existence of this now >>needless Bad Cluster File and refused to make the last tweak. >>In any case, I am temporarily using the drive as a 20GB drive >>until one of: >> - Someone has a solution to move forward. >> - I buy Partition Magic >> - I just create a d: partition (yecch). >> > > I've implemented bad sector support for ntfsresize in April and so far it > worked fine and passes all my tests. Apparently you want to expand NTFS, > right? Yes, the point I am at right now is that I have a 60GB partition containing a 20GB NTFS filesystem. Things are working correctly but not using the extra space. > That should definitely work for you also but shrink is much more trickier > and I just didn't have time to check out all corner cases, that's why it's > not released yet. If you're willing to test (you have already the backup), > I will put it somewhere for testing in the weekend and if it works for you > also then it's really time to send the patch to Anton. I'm willing to give it a try, although I head out of town for several weeks this evening. So I may not be in a position to try until September. > Cheers, > > Szaka Many thanks! Jim |
