From: Eric Sandeen <sandeen@sandeen.net>
To: Volkan YAZICI <volkan.yazici@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Recovering XFS Partition of Type FAT16
Date: Thu, 07 Jul 2011 15:15:22 -0500 [thread overview]
Message-ID: <4E1613DA.5020105@sandeen.net> (raw)
In-Reply-To: <CAP7pH7tt0UyKLVMbvR1FNP_4c_aP5Y_2gAADxG8=xL6fF_xMCg@mail.gmail.com>
On 7/7/11 2:57 PM, Volkan YAZICI wrote:
> On Thu, Jul 7, 2011 at 6:53 PM, Eric Sandeen <sandeen@sandeen.net> wrote:
>> It sounds like something changed your partition table as well as your
>> filesystem. Putting the partition table back in place first probably
>> would have been the better first step, in retrospect.
>>
>> I can't tell for sure, though, what you've done (did you reparition?
>> mkfs? with which tools? what was the xfs_repair output?) so I'm not
>> sure what to tell you at this point.
>
> I was struggling to boot an ISO image from a USB disk, hence I suspect
> that I had probably set the type of the host machine partition
> (/dev/sda1) to FAT16 with fdisk, instead of USB disk partition
well, almost nothing cares about the partition type, really...
not kernel, anyway, and not mount ...
> (/dev/sdb1). Then in the next boot, Linux doesn't come up and
> complained about XFS issues. Hence I rebooted the machine and repaired
> the fs with xfs_repair. This time partition is mounted properly but a
> significant portion of the disk content is missing. Then in the fdisk
> -l output I realized that /dev/sda1 is set to FAT16. (Isn't it strange
> that I can xfs_repair and mount a partition of type FAT16?) Later I
no, not really, (almost) nothing cares about those couple bytes in the
partition table...
> set the type of /dev/sda1 to Linux, but nothing changed. I called
> xfs_repair again and tried mounting again, no luck: same fs size
> (20GB), same missing contents.
>
> For the xfs_repair output... Honestly, I don't remember and I don't
> think I can reproduce the situation.
And I'm afraid I can't really imagine how you got here; apparently
your partition got shrunk, at least - and maybe mkfs'd as FAT?
And I don't think repair will cope well with a truncated block device...
perhaps your handy partitioning tool helpfully mkfs'd for you a few
times, as well...?
-Eric
>
> Best.
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-07-07 20:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 10:23 Recovering XFS Partition of Type FAT16 Volkan YAZICI
2011-07-04 12:49 ` Dave Chinner
2011-07-07 11:32 ` Volkan YAZICI
2011-07-07 15:53 ` Eric Sandeen
2011-07-07 19:57 ` Volkan YAZICI
2011-07-07 20:15 ` Eric Sandeen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E1613DA.5020105@sandeen.net \
--to=sandeen@sandeen.net \
--cc=volkan.yazici@gmail.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox