Re: Really big files?
Greg Freemyer wrote: I just tried to dd the first 163 GB of a raw drive to a image file. It failed at about 145 GB. Should it work? I had plenty of free space. I'm using cygwin.dll ver. 1.5.5 and a recent dd (I think, see cygcheck -s output). === Session Log $ mount -f -b //./physicaldrive2 /dev/todds Just a completely random guess here: Is 'physicaldrive2' an active system drive? IIRC there are some parts of windows that cannot be read by anything but the kernel itself, such as the SAM database (or something along those lines.) If this is the case then you'd have to do the image when the partition is not active. I don't know how or if tools like Ghost get around this. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Really big files?
From: Brian Dessent Sent: Tuesday, December 16, 2003 10:19 PM Greg Freemyer wrote: === Session Log $ mount -f -b //./physicaldrive2 /dev/todds Just a completely random guess here: Is 'physicaldrive2' an active system drive? IIRC there are some parts of windows that cannot be read by anything but the kernel itself, such as the SAM database (or something along those lines.) If this is the case then you'd have to do the image when the partition is not active. I don't know how or if tools like Ghost get around this. Brian Minimal info addition: Symantec's ghost.exe is a AFAIK DOS application, with all the implications - don't know more about it (does it handle NTFS?). PowerQuest's ghost (i.e. Drive Image) does some 'magic' by booting a temporary disk image - for creating the backup (this disk image can be rebuilt using the installed software. Does understand NTFS and at least 'knows about' Linux). /Hannu E K Nevalainen, B.Sc. EE - 59+16.37'N, 17+12.60'E ** on a mailing list; please keep replies on that particular list ** -- printf(LocalTime: UTC+%02d\n,(DST)? 2:1); -- --END OF MESSAGE-- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Really big files?
Greg Freemyer said: I just tried to dd the first 163 GB of a raw drive to a image file. It failed at about 145 GB. Should it work? I had plenty of free space. Another possibility is addressed at: http://www.jsiinc.com/SUBL/tip5500/rh5584.htm (Something justed gleaned off of the samba list.) -- Don Koch [EMAIL PROTECTED] Not speaking for Cognex Corporation. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Really big files?
I recall at least one recent version with WinXP support, so I'd expect that it does support NTFS. Elliott Wilcoxon Hannu E K Nevalainen wrote: From: Brian Dessent Sent: Tuesday, December 16, 2003 10:19 PM Greg Freemyer wrote: === Session Log $ mount -f -b //./physicaldrive2 /dev/todds Just a completely random guess here: Is 'physicaldrive2' an active system drive? IIRC there are some parts of windows that cannot be read by anything but the kernel itself, such as the SAM database (or something along those lines.) If this is the case then you'd have to do the image when the partition is not active. I don't know how or if tools like Ghost get around this. Brian Minimal info addition: Symantec's ghost.exe is a AFAIK DOS application, with all the implications - don't know more about it (does it handle NTFS?). PowerQuest's ghost (i.e. Drive Image) does some 'magic' by booting a temporary disk image - for creating the backup (this disk image can be rebuilt using the installed software. Does understand NTFS and at least 'knows about' Linux). /Hannu E K Nevalainen, B.Sc. EE - 59+16.37'N, 17+12.60'E ** on a mailing list; please keep replies on that particular list ** -- printf(LocalTime: UTC+%02d\n,(DST)? 2:1); -- --END OF MESSAGE-- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ . -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Really big files?
On Tue, 2003-12-16 at 16:41, Don Koch wrote: Greg Freemyer said: I just tried to dd the first 163 GB of a raw drive to a image file. It failed at about 145 GB. Should it work? I had plenty of free space. Another possibility is addressed at: http://www.jsiinc.com/SUBL/tip5500/rh5584.htm (Something justed gleaned off of the samba list.) That appears to be related to open file handling in ntbackup. I don't think it would be relevant. I'm doing a pretty dumb dd command, Not a intellegent Open File Backup type of thing. Greg -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Really big files?
On Tue, 2003-12-16 at 16:19, Brian Dessent wrote: Greg Freemyer wrote: I just tried to dd the first 163 GB of a raw drive to a image file. It failed at about 145 GB. Should it work? I had plenty of free space. I'm using cygwin.dll ver. 1.5.5 and a recent dd (I think, see cygcheck -s output). === Session Log $ mount -f -b //./physicaldrive2 /dev/todds Just a completely random guess here: Is 'physicaldrive2' an active system drive? IIRC there are some parts of windows that cannot be read by anything but the kernel itself, such as the SAM database (or something along those lines.) If this is the case then you'd have to do the image when the partition is not active. I don't know how or if tools like Ghost get around this. Brian No, it is not an active system drive. By chance this drive had its partition table blown away. Win2k is not even assigning it a drive letter. Also, if you look at the dd output dd: writing `/cygdrive/e/full_image': Permission denied 35838209+0 records in 35838208+0 records out You see that the failure was on the write, not on the read. I have over 50 GB free even with that file in place, so I'm definately not short of space. Also, I believe NTFS for Win2k has a 2 TB filesize max., so that should not be a problem. Greg -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Really big files?
If I wanted to troubleshoot this, how would I do it? I imagine strace would produce an unbelievable amount of output. ie. dd fails after 35 million read/write pairs. Also, what package is dd in? If I do try this I will only be able to make one debug pass per day because of how slow the dd runs. (ie. several hours) Greg On Tue, 2003-12-16 at 19:30, Greg Freemyer wrote: On Tue, 2003-12-16 at 16:19, Brian Dessent wrote: Greg Freemyer wrote: I just tried to dd the first 163 GB of a raw drive to a image file. It failed at about 145 GB. Should it work? I had plenty of free space. I'm using cygwin.dll ver. 1.5.5 and a recent dd (I think, see cygcheck -s output). === Session Log $ mount -f -b //./physicaldrive2 /dev/todds Just a completely random guess here: Is 'physicaldrive2' an active system drive? IIRC there are some parts of windows that cannot be read by anything but the kernel itself, such as the SAM database (or something along those lines.) If this is the case then you'd have to do the image when the partition is not active. I don't know how or if tools like Ghost get around this. Brian No, it is not an active system drive. By chance this drive had its partition table blown away. Win2k is not even assigning it a drive letter. Also, if you look at the dd output dd: writing `/cygdrive/e/full_image': Permission denied 35838209+0 records in 35838208+0 records out You see that the failure was on the write, not on the read. I have over 50 GB free even with that file in place, so I'm definately not short of space. Also, I believe NTFS for Win2k has a 2 TB filesize max., so that should not be a problem. Greg -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Really big files?
Greg Freemyer wrote: If I wanted to troubleshoot this, how would I do it? Does the following work - dd if=/dev/zero of=/cygdrive/e/full_image bs=4k count=44430720 That would at least rule out the reading part of it. What about quotas? Recycle bin full? Anything in the Event Log? I'm not sure if strace would be useful here, you'd see a call to write() that returns -1 and errno would hold EPERM. But maybe there'd be more info, I dunno. It would certainly make a huge log file, that's for sure. dd is in the fileutils package. You can find this out for any filename with the package search page: http://cygwin.com/cgi-bin2/package-grep.cgi?grep=%2Fbin%2Fdd.exe Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
