repair HFS+ corruption using known file size and ino numbers
up vote
0
down vote
favorite
I've had a very strange corruption on a volume : all the files & folders are here, and all have 0 bytes, in lieu of the TBs of data it should contain.
Usual solutions (diskUtility repair, fsck, DiskWarrior) do not solve the problem, as far as the system is concerned the system is "clean".
Luck is: I have all the file inode numbers (ino) and file sizes, stored in a sqlLite database that I had created doing media-management.
Question: can I use this file size & ino info to do some manual restore? (for instance with dd from /dev/rdiskXsY)
Two side notes:
it's expected the filesystem to be not at all fragmented, as it's a copy-once / read-many use types, and was recently formatted
my suspect for this corruption is a third party had used an HFS+ driver from windows to create the data; but at one time, in the past, this data was fully readable, not corrupted*
macos filesystem-corruption hfs+ inode
add a comment |
up vote
0
down vote
favorite
I've had a very strange corruption on a volume : all the files & folders are here, and all have 0 bytes, in lieu of the TBs of data it should contain.
Usual solutions (diskUtility repair, fsck, DiskWarrior) do not solve the problem, as far as the system is concerned the system is "clean".
Luck is: I have all the file inode numbers (ino) and file sizes, stored in a sqlLite database that I had created doing media-management.
Question: can I use this file size & ino info to do some manual restore? (for instance with dd from /dev/rdiskXsY)
Two side notes:
it's expected the filesystem to be not at all fragmented, as it's a copy-once / read-many use types, and was recently formatted
my suspect for this corruption is a third party had used an HFS+ driver from windows to create the data; but at one time, in the past, this data was fully readable, not corrupted*
macos filesystem-corruption hfs+ inode
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I've had a very strange corruption on a volume : all the files & folders are here, and all have 0 bytes, in lieu of the TBs of data it should contain.
Usual solutions (diskUtility repair, fsck, DiskWarrior) do not solve the problem, as far as the system is concerned the system is "clean".
Luck is: I have all the file inode numbers (ino) and file sizes, stored in a sqlLite database that I had created doing media-management.
Question: can I use this file size & ino info to do some manual restore? (for instance with dd from /dev/rdiskXsY)
Two side notes:
it's expected the filesystem to be not at all fragmented, as it's a copy-once / read-many use types, and was recently formatted
my suspect for this corruption is a third party had used an HFS+ driver from windows to create the data; but at one time, in the past, this data was fully readable, not corrupted*
macos filesystem-corruption hfs+ inode
I've had a very strange corruption on a volume : all the files & folders are here, and all have 0 bytes, in lieu of the TBs of data it should contain.
Usual solutions (diskUtility repair, fsck, DiskWarrior) do not solve the problem, as far as the system is concerned the system is "clean".
Luck is: I have all the file inode numbers (ino) and file sizes, stored in a sqlLite database that I had created doing media-management.
Question: can I use this file size & ino info to do some manual restore? (for instance with dd from /dev/rdiskXsY)
Two side notes:
it's expected the filesystem to be not at all fragmented, as it's a copy-once / read-many use types, and was recently formatted
my suspect for this corruption is a third party had used an HFS+ driver from windows to create the data; but at one time, in the past, this data was fully readable, not corrupted*
macos filesystem-corruption hfs+ inode
macos filesystem-corruption hfs+ inode
asked Dec 2 at 7:29
MichaelC
76117
76117
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1380125%2frepair-hfs-corruption-using-known-file-size-and-ino-numbers%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown