Jump to content
Division-M Community

Stacy

Members
  • Content Count

    8
  • Joined

  • Last visited

About Stacy

  • Rank
    Newbie
  • Birthday 11/22/1971

Contact Methods

  • Website URL
    http://www.internetguys.ca

Profile Information

  • Gender
    Male
  • Location
    Northern British Columbia
  • Interests
    Big Pools of data !
  1. I have a 60TB pool for a client and am struggling with it it since what I think was Folderwall in version 3.200a messed it all up. I have a ticket in with Anthony but he has not answered any of my questions in 2 days.. so I am not sure if Divisions is shut down for holidays or what is happening. Totally unlike Anthony to not answer my questions. I am quite Desperate for some help so posting here in the hopes that someone has some insight. I wont spell out the entire ticket but the revolving issue is event viewer keeps popping up with these: Warnings: The IO Operation at logical block address 0x21 for Disk 11 (PDO name: \Device\0000004d) was retired. The IO Operation at logical block address 0x11 for Disk 11 (PDO name: \Device\0000004d) was retired. The IO Operation at logical block address 0x01 for Disk 11 (PDO name: \Device\0000004d) was retired. The File System Structure on Volume C:\Program Files\Division-M\Drivebender\System\Mounts\{B941F5A3-8C64-425D-A2AD-71B7ED808C11} has now been repaired. (4 times) Disk 11 is the actual pool Errors: Volume C:\Program Files\Division-M\Drive Bender\System\Mounts\{B941F5A3-8C64-425D-A2AD-71B7ED808C11} (\Device\HarddiskVolume16) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell. The file system structure on volume C:\Program Files\Division-M\Drive Bender\System\Mounts\{B941F5A3-8C64-425D-A2AD-71B7ED808C11} cannot be corrected. Please run the chkdsk utility on the volume C:\Program Files\Division-M\Drive Bender\System\Mounts\{B941F5A3-8C64-425D-A2AD-71B7ED808C11}. A corruption was discovered in the file system structure on volume C:\Program Files\Division-M\Drive Bender\System\Mounts\{B941F5A3-8C64-425D-A2AD-71B7ED808C11}. The file system structure on volume C:\Program Files\Division-M\Drive Bender\System\Mounts\{B941F5A3-8C64-425D-A2AD-71B7ED808C11} cannot be corrected. Please run the chkdsk utility on the volume C:\Program Files\Division-M\Drive Bender\System\Mounts\{B941F5A3-8C64-425D-A2AD-71B7ED808C11}. A corruption was discovered in the file system structure on volume C:\Program Files\Division-M\Drive Bender\System\Mounts\{B941F5A3-8C64-425D-A2AD-71B7ED808C11}. And this one which actually restarted the server: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000005200, 0xffff83849d254000, 0x364c26344a233148, 0xd933bca0ea82e464). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 7206ce76-60c8-40d3-b33c-2fcbb2b9817f. I have taken each drive in the Pool and have mapped it to a drive letter and have ran Check the Drive with Correct any errors found check marked on each drive until they came back with no errors. Also to note: C:\Program Files\Division-M\Drive Bender\System\Mounts\{B941F5A3-8C64-425D-A2AD-71B7ED808C11} - This folder does not exist at this path Yesterday I cleaned up all the Folders.00X on each drive 1 at a time and deleted the recycle bin which was reported as corrupt. Then set Drive bender to perform a Pool Health Check and overnight the system crashed and produced all the information above. I am at a lose how to fix this issue and the only thing I can think to do is it create a new Pool with new Hard Drives in the same machine and migrate the data to it ? Anyone got any suggestions or direction that can help ? Thank much and Merry Christmas, Stacy
  2. LIke most people that use products like DB.. I am a packrat
  3. I make so many typos it is amazing ... the 48 drive question in my very first post was supposed to be 24 drives in 1 pool. Doh!
  4. Sorry I forgot to commment on the Smart question - Smart is showing all drives as good to go. I replace them when Smart warnings appear.
  5. No it has been various drives and has always happened on some scale since I have used WHSV1 Pool and now DB. It is just now that I have so much data on the drives that I am seeing it more often. Certianly I have had drives fail like anyone with lots of drives will and in those cases i ahve to restore files from my backup pool. Trouble is that I have been using Goodsync to sync server1 to server2 and it will unforunately copy the 0 byte file overtop of the good file on the second machine. Perhaps the new Pool to Pool sync in version 2 will not perform this same copy. I have it set so only Administrator and my personal normal Windows user has Write access - everyone else and all devices only have read access, so I am fairly certian it is not user error. I honestly do not know what is causing it I do not think DB has anything to do with the issue, I do think it has to do with the NTFS file system - the more I read about it in comparision to ZFS the more I think NTFS is not that great for large volumes of information. Where as ZFS actaully activately looks and repairs data corruption. I have actaully assembled a 12x 4TB ZFS Pool (38TB) machine under Cent OS and am trying it as we speak, took alot of reading to get to this point and I can tell this set up is not for everyone. So currently will have a 2 x 30TB pools with DB and then this 1 x 38TB ZFS pool and am going to put them all through the same tests and see what is best at least for my case. DB itself is a fantastic product, I have sold many machines with it and used DB in work enviroments since its release and I think it top notch. Anthony is fantastic in his support as well. I look forward to seeing DB V2
  6. Hey W3, Thanks for the reply sorry if I upset you asking these questions. Certianly not my intent to speak negatively about DB. I love DB ! However I have been in the computer business for a long time as well, not 40 years mind you and I have always stored lots of data in various forms starting with labeling of a bunch of drives, sitting on shelf, then the next step up to WHS v1 and now DB. I have 2 machines like i was saying above with DB and one syncs all the data to the second for a backup. On both machine's I am the only 1 who has write access so no one else can over write a file or delete it etc without perhaps malicous intent. What I see is that because my data is growing the 0 byte file issue is appearing more often, and as the data continues to grow it will continue to happen but at a increase rate just simply because there is more information. It is only in the last 3-4 years that we have seen more and more consumer level large data pools so this issue will become more prevalant. More data more chances for whatever is causing this happen more often. Why I mentioned ZFS is because of the way if functions, constantly checking files and comparing them to a checksum to ensure data integrity. I am guessing that as you have been in the Storage arena for all years you must have read an article or 2 on ZFS so my questions is how does DB deal with Data Integrity when compared to ZFS's checksumming of every file as it arrives on the volume. Here is a brief article on ZFS Data Integrity: http://arstechnica.com/staff/2005/12/2049/ ZFS has some very interesting features for maximizing the drives that one has with parity drives for instance so you dont need to mirror everything. However ZFS is FAR from average user friendly from what I can tell, where as DB on the other hand is so simple and amazingly easy to use. Why I am interested in other peoples opinions on large pools and their experiences, as if there is something that I am missing that is the reason for these 0 byte files, I do not even know how to look for it. SL
  7. I currently have a large pool - 30TB + and I find some times video files and movies I know I had are gone, or if the file is there the file will be only 0 bytes. Looking around the web I have run across the term Bit Rot can this be why I am finding this with files ? I am about to break into using 4TB drives and am not getting more and more concerned about the data and how secure my data actually is. Currently I backup my 30TB to a second DB server that is 30TB .. which is not efficient. This makes me think ZFS might be a good idea ... however I am not unix guy. Has anyone tried a 48 drive - DB pool?
  8. Stacy

    Beta v2.0.2.9

    Looking forward to this release Anthony, been putting off adding/swapping drives waiting to use the new interface, say if all of us chip in and send you more coffee can you have it wrapped up by the weekend?
×
×
  • Create New...