HUGE bug in 1.06.15

[juggy]

this is ntfs on a freshly paritioned defragmented drive

something is wrong with the way wdtv live handles ntfs and mkv files or files over a certain size 4gb +?

[Michelo]

In my humble opnion WD is the guilty because I have ubuntu and windows they who reading ntfs without problems 

[TonyPh12345]

---

juggy wrote:

something is wrong with the way wdtv live handles ntfs and mkv files or files over a certain size 4gb +?

---

Not that I've ever seen...  Almost all of my files are over 4GB, some close to 40.

[jlaborde3]

NTFS is just fine - your data loss is not due to a failure to unmount.

[Enforcer]

Same problem for me. When I updated to 1.06.15, I started to notice that some files where becoming 0 bytes.

No matter the file size (>4gb or even very small like subtitles).

Each time I plugged the drive on my Windows 7 machine, Windows had to do a chkdsk.

So far, I downgraded to 1.05.04 and check daily for a new firmware.

I use a WD 2Tb Ntfs formatted harddrive.

Could we know it this bug is open at WD level ?

[whattheheck]

---

RoofingGuy wrote:

The file isn't "written" to, but the file handles that are opened in order to read the file still need to be properly closed.

That's why even if you try to "Safely Remove" a USB drive from Windows, it can't do it if files are still open (even for reads).  All the handles have to be properly released.

Just turning off the power strip, without letting the WDTV close things properly, is kinda bound to cause all kinds of corrupt files and assorted errors.

It's not so much that file system errors were never being generated before... it's just that previous firmwares didn't scan the file system's integrity when first booted.

---

if that is the case under linux, then linux **bleep**. Opening a file for reading should IN NO WAY corrupt the file, even if just turn of the drive (and it won't under windows). Sure you'd leave file locks hanging in memory unless you rebooted or shut down and restarted.

But write corruptions, nope.

[TonyPh12345]

---

whattheheck wrote:

if that is the case under linux, then linux **bleep**. Opening a file for reading should IN NO WAY corrupt the file, even if just turn of the drive (and it won't under windows). Sure you'd leave file locks hanging in memory unless you rebooted or shut down and restarted.

But write corruptions, nope.

---

Sorry, but that is wrong.

Windows and Linux BOTH *write* to the file table EVERY time a file is opened for reading.   Both in NTFS (Windows) and all forms of *nix OS's, which include Mac OS as well.   

The O/S updates the "ATIME," or the time/date of last ACCESS.     You open a file for reading, the ATIME gets updated.

If a file is UPDATED, the MTIME record is updated as well.

Windows and Linux and Macs also have a record called "CTIME," but that is interpreted in different ways depending on the O/S.

Windows uses that time stamp as CREATION time.   Linux / Mac uses that timestamp to record certain types CHANGES to the file record itself (as opposed to the file CONTENTS.)

... so if the modification of the records requires a sector to be relocated (which can happen if the BTREE is being pruned) then those writes can be corrupted, and the BTREE is now corrupt and must be reconstructed.

[Pacman2011]

I have downgraded to 1.05.04 one month ago and no files have been deleted/corrupted in that time span. I never had any problems with files becoming zero bytes in earlier firmwares either.

Something was definitely changed in the latest firmware that causes files to become corrupted!

[Amper]

---

Enforcer wrote:

Same problem for me. When I updated to 1.06.15, I started to notice that some files where becoming 0 bytes.

No matter the file size (>4gb or even very small like subtitles).

Each time I plugged the drive on my Windows 7 machine, Windows had to do a chkdsk.

I use a WD 2Tb Ntfs formatted harddrive.

---

I have this problem. WD Elements Desktop 2 ТB ( WDBAAU0020HBK) + WD TV Live 1.06.15. I checked HDD, it hasn't bad sectors.

I hadn't problem with WD Elements Desktop 1 ТB and 1.06.15.

[Amper]

---

Enforcer wrote:

Same problem for me. When I updated to 1.06.15, I started to notice that some files where becoming 0 bytes.

No matter the file size (>4gb or even very small like subtitles).

Each time I plugged the drive on my Windows 7 machine, Windows had to do a chkdsk.

I use a WD 2Tb Ntfs formatted harddrive.

---

I have this problem. WD Elements Desktop 2 ТB ( WDBAAU0020HBK) + WD TV Live 1.06.15. I checked HDD, it hasn't bad sectors.

[Amper]

I hadn't problem with WD Elements Desktop 1 ТB and 1.06.15.

[juggy]

wd team

this is a critical bug which destroys files

ca n we please get an update on it