On Sun, Nov 11, 2012 at 02:06:25PM +0100, Daniel Baumann wrote:
> i don't think that's a bug.
>
> On 11/11/2012 01:40 PM, Kurt Roeckx wrote:
> > I had a failing disk and wanted to put things on a new disk that
> > happens to be smaller. I started by creating a clone, and then
> > tried to restore it on the new disk.
> >
> > I get the message: "ERROR: Output device too small (X) to fit the
> > NTFS image (Y)."
>
> which is sensible, you cannot 'apply' a clone on a physically too small
> disk.
>
> > So then I tried to run ntfsresize on the image file, which also
> > fails.
>
> did you use a lo device and let ntfsresize operate on the device node?
You mean a loop device? I can't mount it because it's in the
"Special Image Format".
> or, if it's not for a forensic use case (in which you simply wouldn't
> use a smaller than the original disk anyway in the first place), in your
> situation it would be better to format the new disk and copy (as in 'cp
> -a', not as in 'dump') the contents from the loop-mounted image over.
Do you think that "cp -a" will give me a working disk that boots
windows and have things like the sid of the files correct? Copy
all streams of a files? ...
> > So I would like to have an option to either resize on restore on
^^ or
> > resize an image file.
>
> in the light of kiss, i don't think it makese sense to add such
> functionality in ntfsclone as the desired behaviour can be easily
> acchieved by combining standard linux mechanisms.
I don't think Linux even supports all the features of NTFS, so I
don't see how standard linux mechanisms would work. It would make
sense to me to support this on the image file.
Maybe it works on image files, but not when they're in the
"Special Image Format"?
Kurt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
