public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Linda Walsh <lkml@tlinx.org>
Cc: LKML <linux-kernel@vger.kernel.org>, xfs@oss.sgi.com
Subject: Re: 2.6.27.[0,2] problems (v. 2.6.26.5): Samba & root-read-only
Date: Thu, 23 Oct 2008 09:30:05 +1100	[thread overview]
Message-ID: <20081022223005.GV18495@disturbed> (raw)
In-Reply-To: <48FED90F.7030809@tlinx.org>

On Wed, Oct 22, 2008 at 12:41:03AM -0700, Linda Walsh wrote:
> I am having to stay at 2.6.26.5 for now on my main home server.
>
> Going to 2.6.27 (and just trying 2.6.27.2), I'm have two VERY weird (would
> appear to be user-land probs from symptoms), problems. 
>
> 1) Samba -- the system is a Samba domain controller.  When I boot using
> the 2.6.27.2 kernel (or .0 before), I can no longer mount any file systems
> from my windows client. 
.....
>
> 2) My root disk comes up READ-ONLY.  It uses XFS.  I am NOT able to remount
> read/write (mount -o remount,rw /, fails writing to Read-only /etc/mtab,
> mount -n -o remount,rw doesn't give an error message, but doesn't make the
> drive R/W.  Root fs is on an adaptec FAST-SCSI (80MB/s) with an 18MB Seagate
> (root, disk is oldest disk on the system). 

That XFS problem should be fixed in 2.6.27.3, whenever that is going
to be released. It was sent and ACK'd by the stable team a week ago,
but for some reason missed 2.6.27.2.

Most likely is that the Samba problem will be caused by the smbd
not being able to write to it's databases when clients try
to connect because of the read-only root fs.

If you want to patch your kernel, the patch is here:

http://oss.sgi.com/archives/xfs/2008-10/msg00284.html

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2008-10-22 22:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22  7:41 2.6.27.[0,2] problems (v. 2.6.26.5): Samba & root-read-only Linda Walsh
2008-10-22 22:30 ` Dave Chinner [this message]
2008-10-22 22:42   ` Dave Chinner
2008-10-24  0:13   ` Solved: " Linda Walsh

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=20081022223005.GV18495@disturbed \
    --to=david@fromorbit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@tlinx.org \
    --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