Re: [PHP] Very Large File Splatter

[email protected] (Sebastian Krebs)
Newsgroups php.general
Message-ID <CALtuQzD+D2BtUKPZzKg+zw__+19Nx0Aaxm8erss1ckYC8bERsQ@mail.gmail.com>
2013/2/22 Brian Smither <[email protected]>

> PHP 5.4.4-TS-VC9 on Windows XP SP3 NTFS non-system drive with 18GB free.
>
> I dare not try to replicate this. As such, I cannot firmly place the blame
> on PHP.
>
> I have peppered a PHP application with a call to a function which
> appends-only to a logfile the parameters passed to it. Each pass of the
> application creates many MB of content.
>
> It is conceivable that I ran out of hard drive space.
>
> When that which what I was working on seemed to be acting very weird, I
> rebooted the computer only to see thousands of lines scroll by from Windows
> repairing the file system.
>
> I discovered logfile contents in many dozens of files. The timestamp and
> filesize of the damaged files were not changed. Only the contents replaced
> with slices of the logfile.
>
> Again, I'm not going to try to 'intentionally' replicate this, so I ask:
>
> Has PHP's interface with the NTFS file sub-system ever been reported to
> splatter a file across the contents of a drive?
>

Is the PHP-interpreter even possible to create something like this? As far
as I know PHP utilizes the common OS-syscalls to interact with the
filesystem, so it doesn't interact with the harddrive directly, but online
with the FS-driver. Did you shutdown the system cleanly, when you
recognized this behaviour? If not, it would explain, that the windows
assumes the filesystem must be repaired. I can imagine, that this "repair
process" associated the broken data with the wrong file-entries in the
fs-table, which could be an explanation for the behaviour you described.

Regards,
Sebastian


>
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


-- 
github.com/KingCrunch
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.