From: Josef Bacik <jbacik@fusionio.com>
To: "Swâmi Petaramesh" <swami@petaramesh.org>
Cc: Josef Bacik <JBacik@fusionio.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: This time HD LED doesn't come up at all :-(
Date: Thu, 28 Mar 2013 14:01:13 -0400 [thread overview]
Message-ID: <20130328180113.GP28030@localhost.localdomain> (raw)
In-Reply-To: <515467EE.1090105@petaramesh.org>
On Thu, Mar 28, 2013 at 09:55:26AM -0600, Swâmi Petaramesh wrote:
> Le 28/03/2013 14:19, Josef Bacik a écrit :
> > Can you capture the output and post it somewhere so I can see it? Thanks,
> Hi Josef,
>
> I just uploaded the screenshot here: http://dl.free.fr/pRabNdCsf (You
> will need to type in your email address or the list's one to retrieve it)
>
> Meanwhile I did some more tests, and I'm puzzled :
>
> - Booting the latest PartedMagic Live (I believe it's a 3.7.9 kernel), I
> can mount the HD BTRFS filesystem wihtout problem (only tried with
> subvolid=0), I can btrfsck it (unmounted), and it looks allright;
>
> - Still, trying to boot the system the normal way (3.8.0 kernel) fails,
> and I get these errors...
>
> At least the FS doesn't look plain dead, but I have no clue...
>
So can you try a livecd thats 3.8 based and mount manually, and when it hangs
get sysrq+w? The other option is to mount without -o inode_cache and see if
that helps? It looks like you may be hitting some weird deadlock with
inode_cache, but I can't say for sure without sysrq+w so I can see what the
caching thread is doing. Thanks,
Josef
next prev parent reply other threads:[~2013-03-28 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 11:51 This time HD LED doesn't come up at all :-( Swâmi Petaramesh
2013-03-28 13:19 ` Josef Bacik
2013-03-28 15:55 ` Swâmi Petaramesh
2013-03-28 18:01 ` Josef Bacik [this message]
2013-03-28 18:05 ` Josef Bacik
2013-03-28 18:27 ` Swâmi Petaramesh
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=20130328180113.GP28030@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=swami@petaramesh.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