From: Arun Persaud <apersaud@lbl.gov>
To: linux-btrfs@vger.kernel.org
Subject: Re: error 2001, no inode item
Date: Tue, 08 Apr 2014 09:56:45 -0700 [thread overview]
Message-ID: <li19og$m51$1@ger.gmane.org> (raw)
In-Reply-To: <pan$5202e$e473aa9d$bec69d4b$f69d4a7c@cox.net>
Hello
On 04/08/2014 05:10 AM, Duncan wrote:
>[...]
>> I
>> copied all the files from my old HD using dd, converted and then resized
>> the file system. However, my old drive already had some errors.
>
> There's a page on the wiki specifically covering conversion. Please read
> it carefully and follow the recommendations, as the post-ext4-subvolume-
> delete defrag and balance it recommends can prevent problems later.
>
> https://btrfs.wiki.kernel.org/index.php/Conversion_from_Ext3
I did follow instructions from a similar website. The fsck on the ext4
system didn't work though. I also ran the balance command on btrfs, but
I'm not sure anymore, if I ran the defrag.
> [...]
>> Btrfs v3.12+20131125
that's the version I have installed at the moment.
> FWIW, there's a new btrfs-progs v3.14 version available. [...]
>
>>> uname -a
>> Linux apersaud 3.14.0-23.gfa168d7-desktop #1 SMP PREEMPT Tue Apr 1
>> 12:54:08 UTC 2014 (fa168d7) x86_64 x86_64 x86_64 GNU/Linux
>
> Looks like you're up on the kernel, anyway. =:^)
>
>> I'm running opensuse/Tumbleweed.
I'll see if I can get an update for btrfs-progs.
>[...]
> Don't run btrfs check --repair unless you're either told to do so by a
> dev after examining the errors you are seeing, or it's the last desperate
> step before you scrap the filesystem and mkfs anyway, so there's nothing
> to lose.
OK, good to know ;)
>[...]
> And one more thing as a hint to save you some trouble. Strongly consider
> both the noatime (mainly performance) and the autodefrag mount options,
I have noatime, but I'll add autodefrag.
Thanks
Arun
next prev parent reply other threads:[~2014-04-08 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 23:14 error 2001, no inode item Arun Persaud
2014-04-08 12:10 ` Duncan
2014-04-08 16:56 ` Arun Persaud [this message]
2014-05-05 22:22 ` Arun Persaud
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='li19og$m51$1@ger.gmane.org' \
--to=apersaud@lbl.gov \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).