Wildman wrote:
On Tue, 28 Nov 2017 12:39:31 -0600, Char Jackson wrote:
On Tue, 28 Nov 2017 11:35:18 -0600, Wildman wrote:
On Sun, 26 Nov 2017 21:10:10 -0600, Char Jackson wrote:
On Sun, 26 Nov 2017 20:34:26 -0600, wrote:
The SVI folders are all empty.
How are you verifying that? Windows Explorer isn't going to help, but
you can use a few other methods. I use Treesize Free to explore in
there, but Linux should also work. Be careful, though, some folks report
that their PC will no longer boot after mucking around in there.
There is no danger in "reading" a file system no matter
what method or OS you are using. The mucking around
you mentioned would only occur if the user done something
that caused the file system to be written to.
I was being respectful toward frequent contributor "Paul", who has
related his experience that just looking around caused one of his
systems to be unbootable into Windows, unless I'm misunderstanding what
he said. But yes, at least in my case, just looking around has never
caused me any issues.
I mean no disrespect either but, I sand by what I
said. "Mucking around" does not occur as long as
the file system remains read-only. Period.
Well, it surprised the hell out of me.
I was using the "sum" command on the large files
I found in System Volume Information. All of the
large files have a sum of "00000". I thought that
was pretty neat. These could well have been some
representation of a shadow copy.
Well, after I summed those files in SVI (which is *read*
not write), I could no longer boot Windows 7. The
automatic repair tried three times to repair it,
the third pass being a block by block CHKDSK
scan (takes an hour). And nada. Could not recover.
Since I had a backup that coincidentally had
been made only two hours before, I just restored,
rather than make a lifetime research project of it.
I wasn't planning on trashing the OS that day,
and got really lucky on having a backup.
So while I still feel perfectly safe using Linux
for both read and write on NTFS, the experience
did shake my confidence just a tiny bit. And
I feel there is some property of those files
that isn't "normal". The checksum of exactly
zero on each (1GB or so) file, was pretty
weird. What was it reading ? Dunno.
I wouldn't think of writing to those files.
I know better than that. Reading them would change
the "Last Accessed" time, that's assuming Linux
even enables that. On Windows, you can disable
Last Accessed tracking if you want, without side effects
(I think people do that for SSD drive usage).
Paul