All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: linux-kernel@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [RFC PATCH] /sys/block -> /sys/class/block  (Fedora 3 & 4 testers wanted)
Date: Tue, 22 May 2007 17:32:55 -0700	[thread overview]
Message-ID: <20070523003255.GA3675@kroah.com> (raw)
In-Reply-To: <20070522182812.79b53880@gondolin.boeblingen.de.ibm.com>

On Tue, May 22, 2007 at 06:28:12PM +0200, Cornelia Huck wrote:
> On Tue, 22 May 2007 10:25:01 +0200,
> Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
> 
> > I tried this on one of our internal drivers, which is based on FC 3 (or
> > 4, can look this up). With s390 defconfig, it is unable to open the
> > root device /dev/dasda1 (which is unsurprising, considering udev (063)
> > decided to create /dev/dasda(1) as a character node instead of a block
> > node).
> 
> Just to be clear, it's fsck that complains:
> 
> Checking filesystems  
> Checking all file systems.  
> [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/dasda1   
> fsck.ext3: No such device or address while trying to open /dev/dasda1   
> Possibly non-existent or swap device?  
> [FAILED]   
> 
> (so that is after udev has been started and obviously dasda1 could be
> accessed)

But /dev/dasda1 isn't present?  Or why would fsck be complaining here?

> > When I look at the system, /sys/block/ and /sys/class/block/ look sane
> > at first glance (working on a 3270 console is usally PITA...)
> > 
> > Even more surprisingly, the system comes up fine (once I added ptmx to
> > makedev.d/) with CONFIG_SYSFS_DEPRECATED not set. /sys/block/
> > and /sys/class/block/ look just like expected. (Unfortunately, our
> > lsdasd tool breaks with this...)
> > 
> > I'll see if I can find out more.
> 
> I currently have the inkling that
> 
> lrwxrwxrwx  1 root root    0 May 22 15:59 block:dasda1-> ../../../class/block/dasda1
> 
> in /sys/block/dasda/ is the culprit.

Why?

> In all other versions I've tried (without CONFIG_SYSFS_DEPRECATED, and
> on an older kernel with and without CONFIG_SYSFS_DEPRECATED), it's
> always dasda1.

That's just a back symlink, the real device should still be there.

Oh, and yes, you will probably have to have CONFIG_SYSFS_DEPRECATED
enabaled to have a chance for these to work on Fedora 4 or 3.

> I can continue investigating tomorrow, unless someone has a good idea :)

I don't, but any information you can find out would be greatly
appreciated, especially as it seems like it is working, but something is
still a little bit wrong.

thanks,

greg k-h

  reply	other threads:[~2007-05-23  0:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21 23:53 [RFC PATCH] /sys/block -> /sys/class/block (Fedora 3 & 4 testers wanted) Greg KH
2007-05-22  8:25 ` Cornelia Huck
2007-05-22 16:28   ` Cornelia Huck
2007-05-23  0:32     ` Greg KH [this message]
2007-05-23  5:39       ` Cornelia Huck
2007-05-23 18:08         ` Greg KH
2007-05-23 20:34           ` Michael Tokarev
2007-05-23 20:35           ` Michael Tokarev
2007-05-24 14:07             ` Kay Sievers
2007-05-24  6:51           ` Cornelia Huck
  -- strict thread matches above, loose matches on Subject: below --
2007-06-03 18:39 Alan Stern

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=20070523003255.GA3675@kroah.com \
    --to=greg@kroah.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.