backtop


Print 52 comment(s) - last by HrilL.. on Jan 2 at 11:28 AM

Microsoft issues a dire warning that its Home Server product may irreversibly damage pictures, torrents, and other files

Microsoft just announced a big bug that many users of its Windows Home Server users may wish to take note of.  Microsoft warned users not to edit files stored on their Windows Home Servers.  Editing and saving files on a home computer connected to Windows Home Server can lead to data corruption within a week it has been discovered.

Microsoft describes the problem, stating, "When you use certain programs to edit files on a home computer that uses Windows Home Server, the files may become corrupted when you save them to the home server. Several people have reported issues after they have used the following programs to save files to their home servers."

Microsoft details that the following file types are among those affected:

  • Photos
  • Office Outlook files (2007)
  • Office OneNote files (2003/2007)
  • Microsoft Money files
  • Quicken files
  • QuickBooks files
  • Torrent files

Microsoft has not yet announced a concrete schedule for the release of a patch to fix the problem.  It blames the current bug on an internal glitch with Windows Home Servers' shared folders code.  Microsoft is currently trying to reproduce the bug and better understand it.

An anonymous blog was posted on Microsoft's developers pages stating that Microsoft's Windows Home Server Team is working full-time through the holidays to try to fix the problem, so obviously it is a relatively significant issue.

Windows has aggressively tried to market its Home Server products and grow a business in consumer backup storage.  The Windows Home Server software retails for $189.99, while a number of partners produce the physical hardware.  Among these is the HP 500GB EX470, which retails for $599.99. 

So for a total of about $790 you can have a working home server set up for backup operations -- you just probably don't want to back up your pictures, emails, or torrent files on it for now.



Comments     Threshold


This article is over a month old, voting and posting comments is disabled

RE: HP's Home Server Includes the OS
By kkwst2 on 12/28/2007 6:26:17 PM , Rating: 2
That is in fact not what I said. If I'm understanding how the folder share is implemented, you have a local copy and the server copy. It apparently allows you to directly access the server copy and save over it and this causes the corruption.

Should it allow this? Probably not, and as I said in my post it certainly shouldn't cause your files to be corrupted. But should you be saving over the server copy? No. You should be saving it to you local copy and let the server do it's thing - which is to synchronize the files.

It is possible that I'm not understanding how the shares are implemented or am not understanding the bug. Based on what I read in the links, though, that is my understanding of the problem.


RE: HP's Home Server Includes the OS
By mindless1 on 12/29/2007 12:16:10 AM , Rating: 3
It's not that you aren't understanding, it's that you have this arbitrary idea that there's a problem with editing files on a share and saving back to that share. This has worked fine and been done billions upon billions of times ever since the unix terminal days. Only now is this horrible flaw a problem in regular use scenarios.

There is not normally a need to save a local copy, edit that and resave it locally, then depend on the fileserver synchronizing. You've just made things 3X more complex than they need to be when others did what you disagree with fine for many years.

In fact, often users are not allowed to make local copies in the business environment and it is with good reason - you don't want 3 different copies of locally stored files floating around being edited independently, and then there's the increased security risk of multiple points of access to information.


RE: HP's Home Server Includes the OS
By kkwst2 on 12/29/2007 12:51:04 AM , Rating: 2
Well, the model I described has worked for a long time too. It is my understanding that this is the model that WHS is more trying to implement.

Neither is more or less complicated. Saving directly to the server has advantages and disadvantages. For instance, it depends on full-time access to the server, which may not always be practical.

You mention a business environment, which is entirely what this is not intended for.

At any rate, I agree it's a problem. My main point was that I'm not sure this is the way the product was intended to be used.


By rdeegvainl on 12/29/2007 2:45:41 AM , Rating: 2
Well if its a HOME server, full time access better be practical for HOME use. The point of having a server like this is that it is a media dump for your music, pictures and movies. The difference between this and business is that its predominately media instead of being predominately documents. Having multiple copies of something spread out over several machines is just a waste of space and like the previous poster said, a big synchronization issue. Have the one you use, and then your backups on a separate medium. I think that this problem directly affects it's intended use.


RE: HP's Home Server Includes the OS
By afkrotch on 12/31/2007 12:01:58 PM , Rating: 2
The model you described would be an utter failure if there were more than one computer in the network.

Let's say we have 4 computers and one WHS. There are 4 users each accessing file blah.bmp. Each have a copy of the file locally. Each make completely different edits to the file. Exactly what happens when WHS backs up the file? Who's copy gets backed up? Does it attempt to merge the files and corrupt them?

WHS is nothing more than a business product put into homes. WHS is Windows 2003 Server, stripped down of course. I have my own file server at home. It runs Win2k Pro and is on 24/7. I sometimes transfer files locally to the server. Other times I'll save directly to it. WHS is a home product and it should be built around what home users will do.


RE: HP's Home Server Includes the OS
By kkwst2 on 12/31/2007 10:38:40 PM , Rating: 2
Actually, no. It has nothing to do with how many computers are on the network, only how many potential simultaneous users there are. It all depends on the usage model and your goal. For a business share obviously this doesn't make any sense. However, it might make great sense for a home share.

If we're talking about a home product, how likely is it that 4 users are going to use it at once? For me, it would be almost never. My wife, my son, and I would actually never be editing the same file.

However, it is frequently the case that I would want to access a file when I don't have internet access - for instance when I'm on a plane with my laptop. I would want any changes synced to the file server when I get back. To answer the question, if there were multiple copies saved locally, both would be saved, with tags appended to the file name designating which user or computer edited it.

It is certainly based on Windows 2003 but it's not the same product.

At any rate, I guess my comments suggested that I somehow think it's OK that it corrupts files. That's not the case, just that it would not interfere with how I use the product. Of course a product that is designed to back up your files shouldn't corrupt them. While I did suggest that perhaps it wasn't how the product was intended to be used, I wasn't trying to imply that it was OK for files to be corrupted.

I have different ideas than you about what WHS should do and how it should operate. After reading about it, I think it will do what I want. In my original post, I was just trying to clarify what situations the corruption was occurring because I was planning to purchase it and didn't think it would apply to how I would use it. I still think I'll wait until these problems are resolved, but it doesn't look like the current bug would affect me.


"It looks like the iPhone 4 might be their Vista, and I'm okay with that." -- Microsoft COO Kevin Turner

Related Articles













botimage
Copyright 2014 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki