fsck_hfs creashes when repairing Time Machine encrypted volume
| Originator: | sasmito.adibowo | ||
| Number: | rdar://14252909 | Date Originated: | 25 June 2013 |
| Status: | Open | Resolved: | No |
| Product: | Mac OS X | Product Version: | 10.8.4 |
| Classification: | Crash/Data Loss | Reproducible: | Yes |
Summary: I have a Time Machine volume that got corrupted by accidentally flicking the power switch mid-way a backup progress. Now fsck_hfs keeps crashing while trying to repair the volume. Steps to Reproduce: 1. Create an encrypted Time Machine volume (direct-attach, USB). 2. Fill it with several years' worth of data. 3. Try to do a full Time Machine backup on a MacBook. 4. Flick the power switch so that the drive shuts down but not the laptop. 5. Repeat from Step 3 a few times. Expected Results: Disk Utility / fsck_hfs should be able to repair the volume. Actual Results: fsck_hfs crashes mid-way while trying to repair the volume. Regression: There isn't any apparent way to get around this issue, or provide alternative (more stable) implementation of fsck_hfs. Notes: An excerpt of the crash log as follows – the complete crash log is attached. Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fff8c91bd46 __kill + 10 1 libsystem_c.dylib 0x00007fff8a141ec0 __abort + 193 2 libsystem_c.dylib 0x00007fff8a10377d __chk_fail + 35 3 libsystem_c.dylib 0x00007fff8a103886 __snprintf_chk + 150 4 fsck_hfs 0x0000000109bfc186 0x109be4000 + 98694 5 fsck_hfs 0x0000000109bfec74 0x109be4000 + 109684 6 fsck_hfs 0x0000000109bf9f8a 0x109be4000 + 89994 7 fsck_hfs 0x0000000109bf21e7 0x109be4000 + 57831 8 fsck_hfs 0x0000000109bf133f 0x109be4000 + 54079 9 fsck_hfs 0x0000000109c0b1bb 0x109be4000 + 160187 10 libdyld.dylib 0x00007fff86c927e1 start + 1
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!