Thank you guys for the quick response:
looks like no dice with the read only option, same error as before
mount -oro /dev/md1 /files
mount: wrong fs type, bad option, bad superblock on /dev/md1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Throw away the inodes? Does that mean it will get toss the problem data out and
recover the rest?
What units is the error message in, blocks or sectors of the drive? Bytes of
data? If I can do my math right, there are 31 bad ones which makes like
0.0000043% so maybe I wouldn't even lose that much? It was a 500 GB partition
with about 300 GB on it.
The jfsrec sounds pretty promising too. I'm thinking that I should run that
first and then the fsck -f? I'm planning on making a dd image and mount -o loop
'ing it so I don't mess up my original partition.
Thanks again for your help.
P.S. I wasn't sure how to reply to the same thread, so I apologize if this
starts a new one.
----- Original Message ----
From: Dave Kleikamp <[EMAIL PROTECTED]>
To: Taran Lewis <[EMAIL PROTECTED]>
Cc: [email protected]
Sent: Tuesday, July 10, 2007 3:22:14 PM
Subject: Re: [Jfs-discussion] fsck.jfs "CANNOT CONTINUE"
On Tue, 2007-07-10 at 12:44 -0700, Taran Lewis wrote:
> I am trying to recover data from an unmountable JFS partition on Fedora Core
> 6. fsck.jfs gives me this result:
>
>
>
> /sbin/fsck.jfs -n /dev/md1
>
>
> /sbin/fsck.jfs version 1.1.10, 19-Oct-2005
>
>
> processing started: 7/6/2007 20.6.4
>
>
> The current device is: /dev/md1
>
>
> Block size in bytes: 4096
>
>
> Filesystem size in blocks: 122097920
>
>
> **Phase 1 - Check Blocks, Files/Directories, and Directory Entries
>
>
> Secondary file/directory allocation structure (2) is not a correct redundant
> copy of primary structure.
>
>
> cannot repair an allocation error for files and/or directories -728363008
> through -728362977.
>
>
> cannot recover files and/or directories -728363008 through -728362977.
> CANNOT CONTINUE.
>
>
>
> I am getting another HD so that I can make a disk image before running
> fsck -f to try to fix it. Is there anything else that I should be
> trying? Will the fsck -f recover at least a portion of the data?
Have you tried mounting it read-only (mount -oro /mntpt)?
If you run fsck with the -f flag, it will try to throw away those
inodes. (It should be printing them as unsigned, not signed.) You may
be able to recover the rest of the file system. I would try recovering
what you can through a read-only mount first.
--
David Kleikamp
IBM Linux Technology Center
____________________________________________________________________________________
Sucker-punch spam with award-winning protection.
Try the free Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/features_spam.html
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Jfs-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jfs-discussion
