Search the Community

With alternate streams now available on ReFS in Windows 2012 R2 and 8.1 will Drivepool support ReFS volumes in the future? NTFS has been a solid platform for many years, but MS has, with the introduction of ReFS in 2012 provided a real alternative with many new benefits, so I think a lot of us are considering a move to ReFS in the foreseable future especially for the frequent write-once-read-seldom scenarios that most of us have with media libraries and file servers. This is actually not so very different from the ZFS/BTRFS vs. EXT3/EXT4 discussions the linux community has. I am wondering what thoughts you guys have about ReFS and where do you think DrivePool/Scanner is headed with regards to ReFS? regards F. Godskesen "Microsoft Windows 8.1 adds support for ReFS volumes and, compared with Microsoft Windows Server 2012, both Windows Server 2012 R2 and Windows 8.1 add additional features when using ReFS, including alternate data streams and automatic correction of corruption when integrity streams are used on parity spaces." http://en.wikipedia.org/wiki/ReFS http://www.petri.co.il/4-reasons-refs-is-better-than-ntfs.htm http://forum.covecube.com/discussion/1031/refs-support/p1

Hi all, Installs fine - service runs momentarily, then always crashes. Windows Event log shows an Error entry and then 2 Information entries. On occasion I will get an error dialog saying that it cannot connect to IPC, otherwise it just keeps restarting and attempting to connect to the service. I tried the beta, but I wasn't even able to get it fully installed without hanging. Any ideas would be helpful. Thanks everyone. Also, the report file mentioned in the Info event is attached (if that is of any use). Error (Event ID 1000): Faulting application name: Scanner.Service.exe, version: 2.4.0.2928, time stamp: 0x51c08080 Faulting module name: MSVCR80.dll, version: 8.0.50727.8428, time stamp: 0x520b1060 Exception code: 0xc000000d Fault offset: 0x0001477d Faulting process id: 0x19a0 Faulting application start time: 0x01ced456130d027c Faulting application path: C:\Program Files (x86)\StableBit\Scanner\Service\Scanner.Service.exe Faulting module path: C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d\MSVCR80.dll Report Id: 54d0ba17-4049-11e3-be8b-b8ac6fccfd72 Faulting package full name: Faulting package-relative application ID: Information (Event ID 1001): Fault bucket , type 0 Event Name: BEX Response: Not available Cab Id: 0 Problem signature: P1: Scanner.Service.exe P2: 2.4.0.2928 P3: 51c08080 P4: MSVCR80.dll P5: 8.0.50727.8428 P6: 520b1060 P7: 0001477d P8: c000000d P9: 00000000 P10: Attached files: These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Scanner.Service._d61ae16a75eb6171aba40bf654aab686d24088_f8b6f644_084c1490 Analysis symbol: Rechecking for solution: 0 Report Id: 54d0ba17-4049-11e3-be8b-b8ac6fccfd72 Report Status: 4100 Hashed bucket: Fault bucket -343816721, type 5 Event Name: BEX Response: Not available Cab Id: 0 Problem signature: P1: Scanner.Service.exe P2: 2.4.0.2928 P3: 51c08080 P4: MSVCR80.dll P5: 8.0.50727.8428 P6: 520b1060 P7: 0001477d P8: c000000d P9: 00000000 P10: Attached files: These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Scanner.Service._d61ae16a75eb6171aba40bf654aab686d24088_f8b6f644_05781665 Analysis symbol: Rechecking for solution: 0 Report Id: 54d0ba17-4049-11e3-be8b-b8ac6fccfd72 Report Status: 0 Hashed bucket: 73cc220b316df2ec8559735716603f2a Report.wer.txt