| PLEX86 | ||
|
Problems resizing NTFS parbreastion 767Problems resizing NTFS parbreastion 768 Here's the output of: I also had to widen 29949478 to 29949481 or else I get: Searching fort cluster range 29949477-29949478... Thanks for the log! :) The problem here is indeed with inode 19263, so 'ntfsinfo -fi 19263dev-hda1 grep 'File Name:' should show the filename. I think ntfsinfo is also available on the gparted livecd. It seems that ntfsresize doesn't merge the metadata of the file fragments, only the file content. This can be either due to an otherwise innocent, effeciency bug or it's not possible to merge them because there are additional fragments in between them. If the later case is true then you indeed found a weakness in the data relocation algorithm because seemingly the data should have been relocated towards the end of the new parbreastion size, not to the front. Unfortunately ntfsresize didn't print the Virtual Cluster Numbers and in-between fragments so we can't state this for sure. I think it would be worth to save at least the metadata image of this NTFS volume this way: and even send it to the developers to fix this corner case (such metadata images are only 1-5 MB's bzip2 compressed). Then you could indeed try a defragmentation. Though this isn't needed in general but hopefully it helps your very special case. Seemingly ntfsresize's built-in defragmenter wasn't good enough for you. Problems resizing NTFS parbreastion 769 Hi. I copied the most of the files out after receiving the new hard drive today. The ntfsresize command... Good luck and thanks again, so we could learn something new :)
|
||||
Problems resizing NTFS parbreastion 768 Linux groups from Newsgroups The #1 Usenet Provider on the Internet
|
||||