All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Sander <msander@cogeco.ca>
To: buildroot@busybox.net
Subject: [Buildroot] losetup /dev/loop0: No such device or address
Date: Thu, 09 Apr 2009 09:37:08 -0400	[thread overview]
Message-ID: <49DDFA04.8040904@cogeco.ca> (raw)

Hi All,

Im using buildroot-2009.02 on atmel at91sam9g20ek.  It is a fairly stock 
cofiguration. 

When I execute "losetup /dev/loop0 /mnt/flash/backing_file.vfat" i get 
the error "losetup /dev/loop0: No such device or address".    /mnt/flash 
exist and has a mounted jffs2 filesystem on it.As far as I can tell, it 
is working correctly.  I can read/write files. I have checked all the 
obvious suspects (including erroneous error message)

here is the output from mount
# mount                      
rootfs on / type rootfs (rw)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /tmp type tmpfs (rw)
sysfs on /sys type sysfs (rw)
/dev/mtdblock2 on /mnt/flash type jffs2 (rw)

looks like a valid mounted filesystem.

# ls /mnt/flash
backing_file.vfat  hosts

the file I am trying to connect to loop0 definately exists.  I copied 
/etc/hosts to it to verify read/write operation.


here are the /dev/loop* devices
# ls -atl loop*
brw-r-----    1 root     root       7,   0 Dec 31 17:00 loop0
brw-r-----    1 root     root       7,   1 Dec 31 17:00 loop1
 
/dev/loop0 definitely exists and appears to be correctly defined (I think).

Anyone aware of issues using losetup?   Is there some obscure dependency 
I might be missing.  any suggestions on how to debug this short of 
printf() from losetup code?

Regards,

mike

             reply	other threads:[~2009-04-09 13:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 13:37 Mike Sander [this message]
2009-04-09 13:52 ` [Buildroot] losetup /dev/loop0: No such device or address Andreas Schweigstill
2009-04-09 14:15   ` Mike Sander

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=49DDFA04.8040904@cogeco.ca \
    --to=msander@cogeco.ca \
    --cc=buildroot@busybox.net \
    /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.