public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederik Deweerdt <deweerdt@free.fr>
To: Marc Perkel <marc@perkel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Read Only File System?
Date: Fri, 6 Oct 2006 16:32:38 +0000	[thread overview]
Message-ID: <20061006163238.GK352@slug> (raw)
In-Reply-To: <45268412.3040400@perkel.com>

On Fri, Oct 06, 2006 at 09:28:02AM -0700, Marc Perkel wrote:
> Not sure where to ask this question so I'll try here. I have a Raid 0 EXT3 file system that is coming up read 
> only. I don't think it's raid related but not sure why it's stuck on read only.
> 
> When I run mount it shows:
> /dev/md0 on /data type ext3 (rw,noatime)
> 
> But when I attempt (running as root) to change anything I get:
> touch: cannot touch `x': Read-only file system
> 
> When I list the directory I get this:
> drwxr-xr-x    8 root root  4096 Sep 29 15:15 .
> drwxr-xr-x   45 root root  4096 Oct  4 10:42 ..
> drwxr-xr-x    4 root root  4096 Sep 11 03:17 critical
> drwx------    2 root root 16384 Sep 10 22:37 lost+found
> drwxr-xr-x   19 root root  4096 Sep 11 02:07 mirror
> dr-x------   14 root root  4096 Sep  9 09:52 Robin
> drwxr-xr-x    7 root root  4096 Oct  5 02:16 snapshot
> drwxrwxr-x+ 289 root root 12288 Oct  1 03:20 www
> 
> Note the weird permissions on Robin. This happened because I was trying to save data from a crashed Windows 
> NT system and I used rsync to copy the data over. And I noticed the problem around the same time.
> 
> So - what can I do to fix this?
Does your dmesg have some info on this?

Regards,
Frederik

  reply	other threads:[~2006-10-06 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06 16:28 Read Only File System? Marc Perkel
2006-10-06 16:32 ` Frederik Deweerdt [this message]
2006-10-08 11:42 ` Matthias Andree

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=20061006163238.GK352@slug \
    --to=deweerdt@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc@perkel.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