|
From: Richard R. <nt...@fl...> - 2003-11-12 22:40:05
|
Hi Szaka, > > I've just hacked together "ntfsmove", a precursor to ntfsdefrag. > > I think you could even call it ntfsdefrag already. The name "ntfsmove" > is a bit misleading IMHO. It's just a proof of concept, there's a lot to do yet such as making it safe. If I called it defrag, then people are likely to start using it regardless of safety. I will rename it later. > > I wouldn't recommend using it yet, since it's not got any error > > checking. > > I took a quick look and the biggest problem I've seen was that > resize_nonres_attr() could overflow the MFT record. It's not very > probably but it can do happen. Yes, it's a possibility, but for now not a big worry. I'm moving an entire data run at a time so the attribute is only likely to shrink. > BTW, you don't allow ntldr to be moved. Oh, pure paranoia. I looked at the volume and asked myself: What might I regret moving. Currently that list is: all metadata and ntldr. > Why? AFAIK the only requirement is it must be in the root directory I agree. I think the only two that we *mustn't* touch are $Boot and $MFTMirr. But I don't want to keep rebuilding my windows box. > Did you _test_ that it doesn't work on NT4 or you _think_ it wouldn't work? Think. I still want to test the ntldr thing though - I don't trust Windows :-) Cheers, Rich |
