linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "George Spelvin" <linux@horizon.com>
To: dreusser@gmail.com
Cc: linux@horizon.com, linux-ext4@vger.kernel.org
Subject: Re: Issue with bad file system
Date: 19 Nov 2012 01:30:04 -0500	[thread overview]
Message-ID: <20121119063004.4845.qmail@science.horizon.com> (raw)

I'm sorry about your problems, but... a little more information
please?

Mount is very explicitly telling you that there's probably more
information in the kernel logs.  It even gives the command to see it.
WHY DIDN'T YOU INCLUDE IT?  <snark>Was it perhaps too subtle a hint?</snark>

What kernel version are you running?  If it's a distribution kernel,
what kernel?  What architecture?

What does e2fsck say about the file system?
What does dumpe4fs -h /dev/md0 show?


The one odd thing I can see is that md devices *are* usually listed in
/proc/partitions, but it's not showing up in yours.

The output of "cat /proc/mdstat" would also be useful.

             reply	other threads:[~2012-11-19  6:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19  6:30 George Spelvin [this message]
2012-11-19  7:23 ` Issue with bad file system Drew Reusser
2012-11-19  8:32   ` George Spelvin
2012-11-19 15:29     ` Eric Sandeen
2012-11-19 17:00       ` Drew Reusser
2012-11-19 16:57     ` Drew Reusser
2012-11-19 17:14       ` Eric Sandeen
2012-11-19 18:41         ` Theodore Ts'o
2012-11-19 19:15           ` George Spelvin
2012-11-19 19:36             ` Theodore Ts'o
2012-11-19 19:53           ` Drew Reusser
2012-11-19 20:24             ` Theodore Ts'o
2012-11-19 19:54         ` Drew Reusser
2012-11-19 21:15           ` George Spelvin
2012-11-19 21:30             ` Eric Sandeen
  -- strict thread matches above, loose matches on Subject: below --
2012-11-19  4:46 Drew Reusser
2012-11-19 15:18 ` Eric Sandeen

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=20121119063004.4845.qmail@science.horizon.com \
    --to=linux@horizon.com \
    --cc=dreusser@gmail.com \
    --cc=linux-ext4@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).