|
From: Anton A. <ai...@ca...> - 2004-02-28 21:41:01
|
On Sat, 28 Feb 2004, Szakacsits Szabolcs wrote: > On Thu, 26 Feb 2004, Anton Altaparmakov wrote: > There is a high demand for a stable resizer with the relocation support. > Current ntfsresize 1.9-BETA is stable, still no error was reported over > the last 3 months. The things needed to be added are > > - support the very rare cases left > - make code usable for others as functions > > Both of the aboves need heavier changes and although they aren't really in > functionality but they are error-prone. I'm afraid it could just > invalidate the last 3 months successful testing phase. > > What's missing to be released as stable? Well, mostly > > 1) discriminated exit codes thus tools using it would know > what to do or report to users without parsing the ntfsresize > output. That is not a showstopper for a stable release IMO. > 2) if an on-going resize fails for some reason then the modified > $BITMAP won't be saved. This isn't very healthy but > > a) users and integrators are always adviced to make an > explicite resize test run. If that succeds then the > real resize must succeed also. So they can end up in this > situation only if they don't follow the advice. > > b) if they ignored the documents/advices and ended up in > this situation then the scheduled chkdsk should be able > to correct $BITMAP. In my experience, it was always able > to do it correctly. > > My question is what way to proceed? Focus/make a stable release before > heavier changes? If yes then should I implement the $BITMAP saving for > that release? I suggest stable release sooner rather than later. Remember: release often is the secret to success. (-: I would suggest to either implement the $BITMAP saving OR to bolt a big fat warning when ntfsresize aborts saying something like: WARNING! WARNING! WARNING! You MUST let Windows chkdsk test and repair this partition as it has been left in an inconsistent state! Do not attempt to write anything to this partition until it has been repaired by chkdsk! Failure to do so will result in total loss of all data on the partition in the worst case! You have been warned. If that doesn't scare people into letting chkdsk work on the partition nothing will. (-: Whatever you decide just let me know when you are ready and I will make the release. Best regards, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/ |
