On 09/19/2014 08:16 PM, Chris Murphy wrote:
On Sep 19, 2014, at 11:49 AM, jd1008 <jd1008@xxxxxxxxx> wrote:
On 09/19/2014 08:39 AM, Robert Nichols wrote:
On 09/18/2014 10:57 PM, jd1008 wrote:
I ran mkfs.ext3 -S /dev/sdc7
then ran fsck.ext3 -y /dev/sdc7
it blew away EVERYTHING :)
Back to square one and re-dd original to test drive
and start over.
Ouch! That _used_ to work. Trying it just now, "mke3fs -S" seems
to clear a substantial portion of the inodes, which the manpage
specifically says it should _not_ do, and then /fsck/ completes the
destruction by moving all of the remaining inodes to lost+found.
Sorry about that.
Can raise a bug against it?
Chances are this is an upstream bug, or a misunderstanding. You should post your reproduce steps to the ext4 list, what you expect to happen based on man page, and what actually happens.
http://vger.kernel.org/vger-lists.html#linux-ext4
It might be better for someone besides me to do that. I'm running an
RHEL 6 clone, which uses e2fsprogs-1.41.12. If I post on the mailing
list I'll immediately be told to upgrade to the latest version. Since
my ox is not the one being gored here, I'm reluctant to jump through
the hoops needed to do that.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
