Device or resource busy

Device or resource busy

[Stephan Windmüller]

[-- Attachment #1: Type: text/plain, Size: 668 bytes --]

Hello!

On our Ubuntu (8.04) machine we mount home directories from a Solaris
server with NFS and autofs. From time to time users complain that they
are unable to delete any directories. The error message is "Device or
resource busy".

When I look with "nfsstat -m", I can see a lot of mount points for each
user, including the directory which cannot be deleted. One user had a
total of 200 mounts!

My question is: Why does NFS mount each directory seperately?

Here is an example output for a user:

/ldaphome/username from host:/export/username
 Flags: rw,vers=3,rsize=1048576,wsize=1048576,hard,intr,
 proto=tcp,timeo=600,retrans=2,sec=sys,addr=host

TIA
 Stephan

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2321 bytes --]

Re: Device or resource busy

[Trond Myklebust]

On Mon, 2008-10-27 at 14:10 +0100, Stephan Windm=C3=BCller wrote:
> Hello!
>=20
> On our Ubuntu (8.04) machine we mount home directories from a Solaris
> server with NFS and autofs. From time to time users complain that the=
y
> are unable to delete any directories. The error message is "Device or
> resource busy".
>=20
> When I look with "nfsstat -m", I can see a lot of mount points for ea=
ch
> user, including the directory which cannot be deleted. One user had a
> total of 200 mounts!
>=20
> My question is: Why does NFS mount each directory seperately?
>=20
> Here is an example output for a user:
>=20
> /ldaphome/username from host:/export/username
>  Flags: rw,vers=3D3,rsize=3D1048576,wsize=3D1048576,hard,intr,
>  proto=3Dtcp,timeo=3D600,retrans=3D2,sec=3Dsys,addr=3Dhost
>=20
> TIA
>  Stephan

If /export/username is on a different volume from /export on the server=
,
then the NFS client has to mount it as being a different volume on the
client. 'cat /proc/fs/nfsfs/volumes' should be able to tell you if your
server is exporting more than one volume.

Cheers
  Trond

Re: Device or resource busy

[Stephan Windmüller]

[-- Attachment #1: Type: text/plain, Size: 1831 bytes --]

On Mon, 27. Oct 2008, Trond Myklebust wrote:

> > When I look with "nfsstat -m", I can see a lot of mount points for each
> > user, including the directory which cannot be deleted. One user had a
> > total of 200 mounts!
> If /export/username is on a different volume from /export on the server,
> then the NFS client has to mount it as being a different volume on the
> client. 'cat /proc/fs/nfsfs/volumes' should be able to tell you if your
> server is exporting more than one volume.

/export and /export/home/username are different volumes, but I only
share /export/home/username. Also it is not only the homedirectory
itself but many subdirectories which cause this error. A sample output
from 'nfsstat -m':

-----

/home/username from fileserver:/export/home/username
 Flags: rw,vers=3,rsize=1048576,wsize=1048576,hard,intr,proto=tcp,timeo=600,retrans=2,sec=sys,addr=fileserver

/home/username/workspace/ls5/da/text/Konzept from
fileserver:/export/home/username/workspace/ls5/da/text/Konzept
 Flags: rw,vers=3,rsize=1048576,wsize=1048576,hard,intr,proto=tcp,timeo=600,retrans=2,sec=sys,addr=fileserver

/home/username/.eclipse/org.eclipse.platform_3.3.0_1148896627 from
fileserver:/export/home/username/.eclipse/org.eclipse.platform_3.3.0_1148896627
 Flags: rw,vers=3,rsize=1048576,wsize=1048576,hard,intr,proto=tcp,timeo=600,retrans=2,sec=sys,addr=fileserver

[...]

-----

The output from /proc/fs/nfsfs/volumes looks like:

NV SERVER   PORT DEV     FSID
v3 81d91add  801 0:29    1000001009f:0
v3 81d91add  801 0:27    1000001010f:0
v3 81d91ade  801 0:30    100000100f1:0
v3 81d91add  801 0:31    1000001018b:0
v3 81d91add  801 0:26    10000010189:0
v3 81d91ade  801 0:28    100000100ef:0
v3 81d91ade  801 0:32    100000100f6:0
v3 81d91add  801 0:33    10000010192:0

- Stephan

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2321 bytes --]

Re: Device or resource busy

[Trond Myklebust]

On Mon, 2008-10-27 at 15:29 +0100, Stephan Windm=C3=BCller wrote:
> On Mon, 27. Oct 2008, Trond Myklebust wrote:
>=20
> > > When I look with "nfsstat -m", I can see a lot of mount points fo=
r each
> > > user, including the directory which cannot be deleted. One user h=
ad a
> > > total of 200 mounts!
> > If /export/username is on a different volume from /export on the se=
rver,
> > then the NFS client has to mount it as being a different volume on =
the
> > client. 'cat /proc/fs/nfsfs/volumes' should be able to tell you if =
your
> > server is exporting more than one volume.
>=20
> /export and /export/home/username are different volumes, but I only
> share /export/home/username. Also it is not only the homedirectory
> itself but many subdirectories which cause this error. A sample outpu=
t
> from 'nfsstat -m':
>=20
> -----
>=20
> /home/username from fileserver:/export/home/username
>  Flags: rw,vers=3D3,rsize=3D1048576,wsize=3D1048576,hard,intr,proto=3D=
tcp,timeo=3D600,retrans=3D2,sec=3Dsys,addr=3Dfileserver
>=20
> /home/username/workspace/ls5/da/text/Konzept from
> fileserver:/export/home/username/workspace/ls5/da/text/Konzept
>  Flags: rw,vers=3D3,rsize=3D1048576,wsize=3D1048576,hard,intr,proto=3D=
tcp,timeo=3D600,retrans=3D2,sec=3Dsys,addr=3Dfileserver
>=20
> /home/username/.eclipse/org.eclipse.platform_3.3.0_1148896627 from
> fileserver:/export/home/username/.eclipse/org.eclipse.platform_3.3.0_=
1148896627
>  Flags: rw,vers=3D3,rsize=3D1048576,wsize=3D1048576,hard,intr,proto=3D=
tcp,timeo=3D600,retrans=3D2,sec=3Dsys,addr=3Dfileserver
>=20
> [...]
>=20
> -----
>=20
> The output from /proc/fs/nfsfs/volumes looks like:
>=20
> NV SERVER   PORT DEV     FSID
> v3 81d91add  801 0:29    1000001009f:0
> v3 81d91add  801 0:27    1000001010f:0
> v3 81d91ade  801 0:30    100000100f1:0
> v3 81d91add  801 0:31    1000001018b:0
> v3 81d91add  801 0:26    10000010189:0
> v3 81d91ade  801 0:28    100000100ef:0
> v3 81d91ade  801 0:32    100000100f6:0
> v3 81d91add  801 0:33    10000010192:0

Which shows you have at least 5 different volumes mounted from server
129.217.26.221, and 3 different volumes mounted from server
129.217.26.222.
As I said earlier, every time you cross from one volume to another (eve=
n
if it is on the same server), a mountpoint is automatically created.
Otherwise, you would have issues with two different files possibly
sharing the same inode number on the same NFS filesystem.

Cheers
  Trond

Re: Device or resource busy

[Stephan Windmüller]

[-- Attachment #1: Type: text/plain, Size: 472 bytes --]

On Mon, 27. Oct 2008, Trond Myklebust wrote:

> As I said earlier, every time you cross from one volume to another (even
> if it is on the same server), a mountpoint is automatically created.

How do I "cross from one volume to another"? Is there something I can
test to reproduce this behaviour? It seems that not all users have this
problem.

On the server I shared every single home directory instead of
/export/home. Could this be the cause of the problem?

- Stephan

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2321 bytes --]

Re: Device or resource busy

[Andy Adamson]

Hi

On Wed, 2008-10-29 at 16:09 +0100, Stephan Windm=C3=BCller wrote:
> On Mon, 27. Oct 2008, Trond Myklebust wrote:
>=20
> > As I said earlier, every time you cross from one volume to another =
(even
> > if it is on the same server), a mountpoint is automatically created=
=2E
>=20
> How do I "cross from one volume to another"?=20

When a user traverses the NFS namespace on the client, and crosses from
one server volume to another (fsid change) the NFS client software
automagically does a mount. This is required to avoid inode number
collisions.

> Is there something I can
> test to reproduce this behaviour? It seems that not all users have th=
is
> problem.

That's because all users don't traverse the file system in the same way=
=2E

>=20
> On the server I shared every single home directory instead of
> /export/home. Could this be the cause of the problem?
>=20
> - Stephan

Device or resource busy

[Rohit Kulkarni]

Hi,

When trying to set the pan_id for a node, I keep getting device or
resource busy. the "ifdown wpan1" says "interface wpan1 not
configured". "ifconfig wpan1 down" doesn't throw an error but it seems
to be a no-op.  (wpan0 is the fake radio interface and wpan1 is the
at86rf212b module. Also, the error's the same for the wpan0
interface). There was an email on the list about a month ago with the
same problem. Have there been any updates on the issue?

I'm using the tip of the bluetooth-next kernel and the release tarball
for wpan-tools-0.3 on a raspberry pi attached to an at86rf212b module
over spi. Please let me know if I missed out on any relevant info.

Also, when I try to create a coordinator node, I get an "invalid
argument" error. I've added the netlink debug messages from this at
the bottom. Once, I can pair a node and a coordinator, I'd like to
send/receive messages between them from userland code (even broadcast
messages will do for now!). Is it too optimistic yet? Or has it been
done already? If it is already supported, even the simplest of code
samples will save me a lot of time! :)

Thanks!
-Rohit

root@raspberrypi:~#  iwpan --debug phy wpan-phy1 interface add wpan2
type coordinator 00:00:00:00:00:00:00:11
-- Debug: Sent Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [HEADER] 16 octets
    .nlmsg_len = 60
    .nlmsg_type = 21 <0x15>
    .nlmsg_flags = 5 <REQUEST,ACK>
    .nlmsg_seq = 1420839332
    .nlmsg_pid = 2492
  [PAYLOAD] 44 octets
    07 00 00 00 08 00 01 00 01 00 00 00 0a 00 04 00 77 70 ................wp
    61 6e 32 00 00 00 08 00 05 00 02 00 00 00 0c 00 17 00 an2...............
    11 00 00 00 00 00 00 00                               ........
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Received Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [HEADER] 16 octets
    .nlmsg_len = 80
    .nlmsg_type = 2 <ERROR>
    .nlmsg_flags = 0 <>
    .nlmsg_seq = 1420839332
    .nlmsg_pid = 2492
  [ERRORMSG] 20 octets
    .error = -22 "Invalid argument"
  [ORIGINAL MESSAGE] 16 octets
    .nlmsg_len = 16
    .nlmsg_type = 21 <0x15>
    .nlmsg_flags = 5 <REQUEST,ACK>
    .nlmsg_seq = 1420839332
    .nlmsg_pid = 2492
---------------------------  END NETLINK MESSAGE   ---------------------------
command failed: Invalid argument (-22)
root@raspberrypi:~#

Re: Device or resource busy

[Alexander Aring]

On Tue, Jan 20, 2015 at 05:58:45PM +0530, Rohit Kulkarni wrote:
> Hi,
> 
> When trying to set the pan_id for a node, I keep getting device or
> resource busy. the "ifdown wpan1" says "interface wpan1 not
> configured". "ifconfig wpan1 down" doesn't throw an error but it seems
> to be a no-op.  (wpan0 is the fake radio interface and wpan1 is the
> at86rf212b module. Also, the error's the same for the wpan0
> interface). There was an email on the list about a month ago with the
> same problem. Have there been any updates on the issue?
> 

I can't reproduce the issue with the -EBUSY error. This should be fixed
by a ifdown of the interface before.

I don't know where the printout "interface wpan1 not configured" comes
from.

For doing a ifdown:

I use "ip" rather than "ifconfig". I will show some example: at beginning
we have a wpan0 interface which is down:

`ip link show wpan0`:

2: wpan0: <BROADCAST,NOARP> mtu 127 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ieee802.15.4 94:8a:f5:4c:b3:b6:da:ff brd ff:ff:ff:ff:ff:ff:ff:ff

after calling `ip link set wpan0 up` we have:

2: wpan0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 127 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000
    link/ieee802.15.4 94:8a:f5:4c:b3:b6:da:ff brd ff:ff:ff:ff:ff:ff:ff:ff

Notice the netdev flag changes to "UP". Please check that on your side.

The fakelb driver:

Also I would not use the fake driver, there is a huge TODO list on my side
for this driver. When I used this driver the first time, I detected
that the driver received the frames which actual the driver actual sending,
Which is wrong.

Additional the fakelb driver makes no sense with only one fake registered
phy. We need to update the whole driver and documentation. I would mark this
driver as broken.

> I'm using the tip of the bluetooth-next kernel and the release tarball
> for wpan-tools-0.3 on a raspberry pi attached to an at86rf212b module
> over spi. Please let me know if I missed out on any relevant info.
> 
> Also, when I try to create a coordinator node, I get an "invalid
> argument" error. I've added the netlink debug messages from this at
> the bottom. Once, I can pair a node and a coordinator, I'd like to
> send/receive messages between them from userland code (even broadcast
> messages will do for now!). Is it too optimistic yet? Or has it been
> done already? If it is already supported, even the simplest of code
> samples will save me a lot of time! :)
> 

Sorry, coordinator support isn't available yet. But you could use a node
interface and sending via RAW socket interface. Furthermore the should be a
coordinator interface and some netlink commands do to such MLME ops...
then handling with coordinators would be easily. There exists also no MLME
ops for node interfaces, so you need to do the pan association full
inside userspace via RAW sockets.

Currently, we handling dataframes via DGRAM and 6LoWPAN only.

- Alex

Re: Device or resource busy

[Rohit Kulkarni]

Hi Alex,

I tried the "ip link set" command but the wpan interface doesn't go
down. The wpan1 device is already UP on boot and setting the channel
works fine but it fails with -EBUSY when trying to set pan_id.

Also, can you please point me to some existing code that uses the RAW
socket interface to communicate over 6LoWPAN?

Thanks again!
-Rohit

Here's the output from "ip link ..."(wpan-phy1 / wpan1 is the
at86rf212b device):

root@raspberrypi:~# iwpan list
wpan_phy wpan-phy1
supported channels:
page 0: 0,1,2,3,4,5,6,7,8,9,10
page 2: 0,1,2,3,4,5,6,7,8,9,10
current_page: 0
current_channel: 5
cca_mode: 1
tx_power: 0
wpan_phy wpan-phy0
supported channels:
page 0: 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26
page 1: 0,1,2,3,4,5,6,7,8,9,10
page 2: 0,1,2,3,4,5,6,7,8,9,10
page 3: 0,1,2,3,4,5,6,7,8,9,10,11,12,13
page 4: 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15
page 5: 0,1,2,3,4,5,6,7
page 6: 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21
current_page: 0
current_channel: 0
cca_mode: 0
tx_power: 0

root@raspberrypi:~# ip link show wpan1
3: wpan1: <BROADCAST,NOARP,UP,LOWER_UP> mtu 127 qdisc pfifo_fast state
UNKNOWN mode DEFAULT qlen 300
    link/ieee802.15.4 29:12:0f:cb:3a:39:8a:69 brd ff:ff:ff:ff:ff:ff:ff:ff

root@raspberrypi:~# ip link set wpan1 down

root@raspberrypi:~# ip link show wpan1
3: wpan1: <BROADCAST,NOARP,UP,LOWER_UP> mtu 127 qdisc pfifo_fast state
UNKNOWN mode DEFAULT qlen 300
    link/ieee802.15.4 29:12:0f:cb:3a:39:8a:69 brd ff:ff:ff:ff:ff:ff:ff:ff

root@raspberrypi:~# ip link set wpan1 up

root@raspberrypi:~# ip link show wpan1
3: wpan1: <BROADCAST,NOARP,UP,LOWER_UP> mtu 127 qdisc pfifo_fast state
UNKNOWN mode DEFAULT qlen 300
    link/ieee802.15.4 29:12:0f:cb:3a:39:8a:69 brd ff:ff:ff:ff:ff:ff:ff:ff
root@raspberrypi:~#

On Wed, Jan 21, 2015 at 1:14 AM, Alexander Aring <alex.aring@gmail.com> wrote:
> On Tue, Jan 20, 2015 at 05:58:45PM +0530, Rohit Kulkarni wrote:
>> Hi,
>>
>> When trying to set the pan_id for a node, I keep getting device or
>> resource busy. the "ifdown wpan1" says "interface wpan1 not
>> configured". "ifconfig wpan1 down" doesn't throw an error but it seems
>> to be a no-op.  (wpan0 is the fake radio interface and wpan1 is the
>> at86rf212b module. Also, the error's the same for the wpan0
>> interface). There was an email on the list about a month ago with the
>> same problem. Have there been any updates on the issue?
>>
>
> I can't reproduce the issue with the -EBUSY error. This should be fixed
> by a ifdown of the interface before.
>
> I don't know where the printout "interface wpan1 not configured" comes
> from.
>
> For doing a ifdown:
>
> I use "ip" rather than "ifconfig". I will show some example: at beginning
> we have a wpan0 interface which is down:
>
> `ip link show wpan0`:
>
> 2: wpan0: <BROADCAST,NOARP> mtu 127 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
>     link/ieee802.15.4 94:8a:f5:4c:b3:b6:da:ff brd ff:ff:ff:ff:ff:ff:ff:ff
>
> after calling `ip link set wpan0 up` we have:
>
> 2: wpan0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 127 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000
>     link/ieee802.15.4 94:8a:f5:4c:b3:b6:da:ff brd ff:ff:ff:ff:ff:ff:ff:ff
>
> Notice the netdev flag changes to "UP". Please check that on your side.
>
> The fakelb driver:
>
> Also I would not use the fake driver, there is a huge TODO list on my side
> for this driver. When I used this driver the first time, I detected
> that the driver received the frames which actual the driver actual sending,
> Which is wrong.
>
> Additional the fakelb driver makes no sense with only one fake registered
> phy. We need to update the whole driver and documentation. I would mark this
> driver as broken.
>
>> I'm using the tip of the bluetooth-next kernel and the release tarball
>> for wpan-tools-0.3 on a raspberry pi attached to an at86rf212b module
>> over spi. Please let me know if I missed out on any relevant info.
>>
>> Also, when I try to create a coordinator node, I get an "invalid
>> argument" error. I've added the netlink debug messages from this at
>> the bottom. Once, I can pair a node and a coordinator, I'd like to
>> send/receive messages between them from userland code (even broadcast
>> messages will do for now!). Is it too optimistic yet? Or has it been
>> done already? If it is already supported, even the simplest of code
>> samples will save me a lot of time! :)
>>
>
> Sorry, coordinator support isn't available yet. But you could use a node
> interface and sending via RAW socket interface. Furthermore the should be a
> coordinator interface and some netlink commands do to such MLME ops...
> then handling with coordinators would be easily. There exists also no MLME
> ops for node interfaces, so you need to do the pan association full
> inside userspace via RAW sockets.
>
> Currently, we handling dataframes via DGRAM and 6LoWPAN only.
>
> - Alex

Re: Device or resource busy

[Maciej Wasilak]

Hello

2015-01-21 11:30 GMT+01:00 Rohit Kulkarni <rmkulkar@gmail.com>:
> I tried the "ip link set" command but the wpan interface doesn't go
> down. The wpan1 device is already UP on boot and setting the channel
> works fine but it fails with -EBUSY when trying to set pan_id.

I wrote the previous email about that problem. I experienced same
issues as Rohit. It seems that problem doesn't occur on all platforms.
Two related questions:

1. Is it possible that this issue is somehow related to distro (we
both use Raspbian)?
2. Is it possible that this issue is caused by improper device tree
information? Maybe something changed in device tree handling in last 3
months?

Best Regards
Maciek

Re: Device or resource busy

[Rohit Kulkarni]

Argh! My phone doesn't send plain-text emails. Re-adding linux-wpan.

I'm not sure what you mean by modified device tree. In the device
tree, all I did was add my at86rf212b module as an spi device to the
bcm2835-rpi-b-plus.dts.

-Rohit

On Wed, Jan 21, 2015 at 6:39 PM, Maciej Wasilak <wasilak@gmail.com> wrote:
> Aha - that's very similar situation. I also added u-boot and
> bluetooth-next kernel. Are you using modifed device tree?
>
> 3 months ago I used linux-wpan-next kernel also with Raspbian, and old
> userspace tools and everything worked fine.
>
> Maciek
>
> 2015-01-21 14:04 GMT+01:00 Rohit Kulkarni <rmkulkar@gmail.com>:
>> I'm using the raspbian distro that came with noobs (from sometime in
>> December) and just added u-boot and the bluetooth-next kernel.
>>
>> -Rohit
>> ________________________________
>> From: Maciej Wasilak
>> Sent: ‎21-‎01-‎2015 18:13
>> To: Rohit Kulkarni
>>
>> Subject: Re: Device or resource busy
>>
>> Hello,
>>
>> I'm also running bluetooth-next. I replaced normal 3.12 kernel in
>> Raspbian with bluetooth-next. Which distro you are using?
>>
>> Best Regards
>> Maciek
>>
>> 2015-01-21 13:18 GMT+01:00 Rohit Kulkarni <rmkulkar@gmail.com>:
>>> Hi all,
>>>
>>> I'm now on bluetooth-next and still seeing the problem. So, definitely
>>> doesn't look like a raspbian issue.
>>>
>>> -Rohit
>>> ________________________________
>>> From: Maciej Wasilak
>>> Sent: ‎21-‎01-‎2015 17:28
>>> To: Rohit Kulkarni
>>> Cc: Alexander Aring; linux-wpan@vger.kernel.org
>>> Subject: Re: Device or resource busy
>>>
>>> Hello
>>>
>>> 2015-01-21 11:30 GMT+01:00 Rohit Kulkarni <rmkulkar@gmail.com>:
>>>> I tried the "ip link set" command but the wpan interface doesn't go
>>>> down. The wpan1 device is already UP on boot and setting the channel
>>>> works fine but it fails with -EBUSY when trying to set pan_id.
>>>
>>> I wrote the previous email about that problem. I experienced same
>>> issues as Rohit. It seems that problem doesn't occur on all platforms.
>>> Two related questions:
>>>
>>> 1. Is it possible that this issue is somehow related to distro (we
>>> both use Raspbian)?
>>> 2. Is it possible that this issue is caused by improper device tree
>>> information? Maybe something changed in device tree handling in last 3
>>> months?
>>>
>>> Best Regards
>>> Maciek

Re: Device or resource busy

[Alexander Aring]

Hi,

On Wed, Jan 21, 2015 at 05:48:36PM +0530, Rohit Kulkarni wrote:
> Hi all,
> 
> I'm now on bluetooth-next and still seeing the problem. So, definitely doesn't look like a raspbian issue.
> 

Can you please check if an ifdown/ifup of your loopback interface works?
Usually name of the interface is "lo". If this works, then we know
it's a 802.15.4 specfic issue and we can do more detailed debugging
steps.

Thanks.

- Alex

Re: Device or resource busy

[Rohit Kulkarni]

Hi,

ifdown/ifup also doesn't work on loopback and eth0! So this looks like
a larger issue. Any ideas where I can get help for this?

-Rohit

On Wed, Jan 21, 2015 at 9:16 PM, Alexander Aring <alex.aring@gmail.com> wrote:
> Hi,
>
> On Wed, Jan 21, 2015 at 05:48:36PM +0530, Rohit Kulkarni wrote:
>> Hi all,
>>
>> I'm now on bluetooth-next and still seeing the problem. So, definitely doesn't look like a raspbian issue.
>>
>
> Can you please check if an ifdown/ifup of your loopback interface works?
> Usually name of the interface is "lo". If this works, then we know
> it's a 802.15.4 specfic issue and we can do more detailed debugging
> steps.
>
> Thanks.
>
> - Alex

Re: Device or resource busy

[Alexander Aring]

Hi,

On Thu, Jan 22, 2015 at 01:29:24PM +0530, Rohit Kulkarni wrote:
> Hi,
> 
> ifdown/ifup also doesn't work on loopback and eth0! So this looks like
> a larger issue. Any ideas where I can get help for this?
> 

can you please send the output of:

`strace -f ifconfig wpan0 down`

Additional please give more information about your ifconfig version, is
it a busybox one? Ff yes then please tell us the busybox version.

Then maybe I can help you, otherwise maybe netdev or raspbian forums?

Thanks.

- Alex

Re: Device or resource busy

[Maciej Wasilak]

Hello,

2015-01-22 21:59 GMT+01:00 Alexander Aring <alex.aring@gmail.com>:
> can you please send the output of:
>
> `strace -f ifconfig wpan0 down`
>

pi@raspberrypi ~ $ sudo strace -f ifconfig wpan0 down
execve("/sbin/ifconfig", ["ifconfig", "wpan0", "down"], [/* 23 vars */]) = 0
brk(0)                                  = 0x2f9000
uname({sys="Linux", node="raspberrypi", ...}) = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb6fab000
access("/etc/ld.so.preload", R_OK)      = 0
open("/etc/ld.so.preload", O_RDONLY)    = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=44, ...}) = 0
mmap2(NULL, 44, PROT_READ|PROT_WRITE, MAP_PRIVATE, 3, 0) = 0xb6faa000
close(3)                                = 0
open("/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\270\4\0\0004\0\0\0"...,
512) = 512
lseek(3, 7276, SEEK_SET)                = 7276
read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
1080) = 1080
lseek(3, 7001, SEEK_SET)                = 7001
read(3, "A.\0\0\0aeabi\0\1$\0\0\0\0056\0\6\6\10\1\t\1\n\2\22\4\24\1\25"...,
47) = 47
fstat64(3, {st_mode=S_IFREG|0755, st_size=10170, ...}) = 0
mmap2(NULL, 39740, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0xb6f7e000
mprotect(0xb6f80000, 28672, PROT_NONE)  = 0
mmap2(0xb6f87000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1) = 0xb6f87000
close(3)                                = 0
munmap(0xb6faa000, 44)                  = 0
open("/etc/ld.so.cache", O_RDONLY)      = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=56299, ...}) = 0
mmap2(NULL, 56299, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb6f70000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/lib/arm-linux-gnueabihf/libgcc_s.so.1", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0P\364\0\0004\0\0\0"...,
512) = 512
lseek(3, 129288, SEEK_SET)              = 129288
read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
1160) = 1160
lseek(3, 128956, SEEK_SET)              = 128956
read(3, "A2\0\0\0aeabi\0\1(\0\0\0\0056\0\6\6\10\1\t\1\n\2\22\4\24\1\25"...,
51) = 51
fstat64(3, {st_mode=S_IFREG|0644, st_size=130448, ...}) = 0
mmap2(NULL, 161780, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0xb6f48000
mprotect(0xb6f68000, 28672, PROT_NONE)  = 0
mmap2(0xb6f6f000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1f) = 0xb6f6f000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/lib/arm-linux-gnueabihf/libc.so.6", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\230y\1\0004\0\0\0"...,
512) = 512
lseek(3, 1198880, SEEK_SET)             = 1198880
read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
1360) = 1360
lseek(3, 1198444, SEEK_SET)             = 1198444
read(3, "A.\0\0\0aeabi\0\1$\0\0\0\0056\0\6\6\10\1\t\1\n\2\22\4\24\1\25"...,
47) = 47
fstat64(3, {st_mode=S_IFREG|0755, st_size=1200240, ...}) = 0
mmap2(NULL, 1242408, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE,
3, 0) = 0xb6e18000
mprotect(0xb6f3b000, 28672, PROT_NONE)  = 0
mmap2(0xb6f42000, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x122) = 0xb6f42000
mmap2(0xb6f45000, 9512, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb6f45000
close(3)                                = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb6faa000
set_tls(0xb6faa4c0, 0xb6faab98, 0xb6fae048, 0xb6faa4c0, 0xb6fae048) = 0
mprotect(0xb6f42000, 8192, PROT_READ)   = 0
mprotect(0x1d000, 4096, PROT_READ)      = 0
mprotect(0xb6fad000, 4096, PROT_READ)   = 0
munmap(0xb6f70000, 56299)               = 0
brk(0)                                  = 0x2f9000
brk(0x31a000)                           = 0x31a000
open("/usr/lib/locale/locale-archive", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=2959760, ...}) = 0
mmap2(NULL, 2097152, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb6c18000
mmap2(NULL, 1179648, PROT_READ, MAP_PRIVATE, 3, 0x1b3) = 0xb6af8000
close(3)                                = 0
open("/usr/share/locale/locale.alias", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=2570, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb6fa9000
read(3, "# Locale name alias data base.\n#"..., 4096) = 2570
read(3, "", 4096)                       = 0
close(3)                                = 0
munmap(0xb6fa9000, 4096)                = 0
open("/usr/lib/locale/en_US/LC_MESSAGES", O_RDONLY) = -1 ENOENT (No
such file or directory)
open("/usr/lib/locale/en/LC_MESSAGES", O_RDONLY) = -1 ENOENT (No such
file or directory)
uname({sys="Linux", node="raspberrypi", ...}) = 0
access("/proc/net", R_OK)               = 0
access("/proc/net/unix", R_OK)          = 0
socket(PF_FILE, SOCK_DGRAM, 0)          = 3
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 4
access("/proc/net/if_inet6", R_OK)      = 0
socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 5
access("/proc/net/ax25", R_OK)          = -1 ENOENT (No such file or directory)
access("/proc/net/nr", R_OK)            = -1 ENOENT (No such file or directory)
access("/proc/net/rose", R_OK)          = -1 ENOENT (No such file or directory)
access("/proc/net/ipx", R_OK)           = -1 ENOENT (No such file or directory)
access("/proc/net/appletalk", R_OK)     = -1 ENOENT (No such file or directory)
access("/proc/sys/net/econet", R_OK)    = -1 ENOENT (No such file or directory)
access("/proc/sys/net/ash", R_OK)       = -1 ENOENT (No such file or directory)
access("/proc/net/x25", R_OK)           = -1 ENOENT (No such file or directory)
ioctl(4, SIOCGIFFLAGS, {ifr_name="wpan0",
ifr_flags=IFF_UP|IFF_BROADCAST|IFF_RUNNING|IFF_NOARP}) = 0
ioctl(4, SIOCSIFFLAGS, {ifr_name="wpan0",
ifr_flags=IFF_BROADCAST|IFF_RUNNING|IFF_NOARP}) = 0
exit_group(0)                           = ?



> Additional please give more information about your ifconfig version, is
> it a busybox one? Ff yes then please tell us the busybox version.
>

ifconfig seems to be part of net-tools package - no mention of busybox anywhere:

pi@raspberrypi ~ $ dpkg -s net-tools
Package: net-tools
Status: install ok installed
Priority: important
Section: net
Installed-Size: 834
Maintainer: net-tools Team <pkg-net-tools-maintainers@lists.alioth.debian.org>
Architecture: armhf
Version: 1.60-24.2
Replaces: ja-trans (<= 0.8-2), netbase (<< 4.00)
Depends: libc6 (>= 2.13-28), libgcc1 (>= 1:4.4.0)
Conflicts: ja-trans (<= 0.8-2)
Description: The NET-3 networking toolkit
 This package includes the important tools for controlling the network
 subsystem of the Linux kernel.  This includes arp, ifconfig, netstat,
 rarp, nameif and route.  Additionally, this package contains utilities
 relating to particular network hardware types (plipconfig, slattach,
 mii-tool) and advanced aspects of IP configuration (iptunnel, ipmaddr).
 .
 In the upstream package 'hostname' and friends are included. Those are
 not installed by this package, since there is a special "hostname*.deb".
Homepage: http://net-tools.berlios.de/


Thanks for your help!
Maciek

Re: Device or resource busy

[Alexander Aring]

Hi,

On Thu, Jan 22, 2015 at 10:58:32PM +0100, Maciej Wasilak wrote:
...
> socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 4
> access("/proc/net/if_inet6", R_OK)      = 0
> socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 5
> access("/proc/net/ax25", R_OK)          = -1 ENOENT (No such file or directory)
> access("/proc/net/nr", R_OK)            = -1 ENOENT (No such file or directory)
> access("/proc/net/rose", R_OK)          = -1 ENOENT (No such file or directory)
> access("/proc/net/ipx", R_OK)           = -1 ENOENT (No such file or directory)
> access("/proc/net/appletalk", R_OK)     = -1 ENOENT (No such file or directory)
> access("/proc/sys/net/econet", R_OK)    = -1 ENOENT (No such file or directory)
> access("/proc/sys/net/ash", R_OK)       = -1 ENOENT (No such file or directory)
> access("/proc/net/x25", R_OK)           = -1 ENOENT (No such file or directory)
> ioctl(4, SIOCGIFFLAGS, {ifr_name="wpan0",
> ifr_flags=IFF_UP|IFF_BROADCAST|IFF_RUNNING|IFF_NOARP}) = 0
> ioctl(4, SIOCSIFFLAGS, {ifr_name="wpan0",
> ifr_flags=IFF_BROADCAST|IFF_RUNNING|IFF_NOARP}) = 0
> exit_group(0)                           = ?
> 

I see no issues here. The values also readback and there is no "IFF_UP"
in the last ioctl of file descriptor 4.

Do you are sure that there is no daemon running or something else which
automatically ifup the interface again if you want to set it down? Maybe
just mv the /etc/$NETWORKING_STUFF into a separate directory and try again.

- Alex

Re: Device or resource busy

[Alexander Aring]

On Thu, Jan 22, 2015 at 11:20:13PM +0100, Alexander Aring wrote:
> Hi,
> 
> On Thu, Jan 22, 2015 at 10:58:32PM +0100, Maciej Wasilak wrote:
> ...
> > socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 4
> > access("/proc/net/if_inet6", R_OK)      = 0
> > socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 5
> > access("/proc/net/ax25", R_OK)          = -1 ENOENT (No such file or directory)
> > access("/proc/net/nr", R_OK)            = -1 ENOENT (No such file or directory)
> > access("/proc/net/rose", R_OK)          = -1 ENOENT (No such file or directory)
> > access("/proc/net/ipx", R_OK)           = -1 ENOENT (No such file or directory)
> > access("/proc/net/appletalk", R_OK)     = -1 ENOENT (No such file or directory)
> > access("/proc/sys/net/econet", R_OK)    = -1 ENOENT (No such file or directory)
> > access("/proc/sys/net/ash", R_OK)       = -1 ENOENT (No such file or directory)
> > access("/proc/net/x25", R_OK)           = -1 ENOENT (No such file or directory)
> > ioctl(4, SIOCGIFFLAGS, {ifr_name="wpan0",
> > ifr_flags=IFF_UP|IFF_BROADCAST|IFF_RUNNING|IFF_NOARP}) = 0
> > ioctl(4, SIOCSIFFLAGS, {ifr_name="wpan0",
> > ifr_flags=IFF_BROADCAST|IFF_RUNNING|IFF_NOARP}) = 0
> > exit_group(0)                           = ?
> > 
> 
> I see no issues here. The values also readback and there is no "IFF_UP"
> in the last ioctl of file descriptor 4.
> 
> Do you are sure that there is no daemon running or something else which
> automatically ifup the interface again if you want to set it down? Maybe
> just mv the /etc/$NETWORKING_STUFF into a separate directory and try again.
> 

Maybe something like this?

http://unix.stackexchange.com/questions/50602/cant-ifdown-eth0-main-interface

- Alex

Re: Device or resource busy

[Maciej Wasilak]

Hello,

2015-01-23 8:59 GMT+01:00 Alexander Aring <alex.aring@gmail.com>:
>> Do you are sure that there is no daemon running or something else which
>> automatically ifup the interface again if you want to set it down? Maybe
>> just mv the /etc/$NETWORKING_STUFF into a separate directory and try again.

After your pointers I've found the answer on one of the forums - the
problem is caused by ifplugd service, which automatically brings up
wpan0 interface after it is brought down.
It seems that in previous branch (linux-wpan-next) this problem didn't
exist, because wpan0 interface had to be manually created (and ifplugd
didn't mess with it).

Solution 1 (blunt): killall ifplugd

Solution 2: edit /etc/default/ifplugd

My working /etc/default/ifplugd below:
____

# This file may be changed either manually or by running dpkg-reconfigure.
#
# N.B.: dpkg-reconfigure deletes everything from this file except for
# the assignments to variables INTERFACES, HOTPLUG_INTERFACES, ARGS and
# SUSPEND_ACTION.  When run it uses the current values of those variables
# as their default values, thus preserving the administrator's changes.
#
# This file is sourced by both the init script /etc/init.d/ifplugd and
# the udev script /lib/udev/ifplugd.agent to give default values.
# The init script starts ifplugd for all interfaces listed in
# INTERFACES, and the udev script starts ifplugd for all interfaces
# listed in HOTPLUG_INTERFACES. The special value all starts one
# ifplugd for all interfaces being present.
INTERFACES="eth0"
HOTPLUG_INTERFACES="eth0"
ARGS="-q -f -u0 -d10 -w -I"
SUSPEND_ACTION="stop"

Thank you very much for your help!!!

Regards
Maciek

Re: Device or resource busy

[Alexander Aring]

On Sun, Jan 25, 2015 at 12:36:06PM +0100, Maciej Wasilak wrote:
>
...
> 
> Thank you very much for your help!!!
> 

you're welcome.

- Alex

Re: Device or resource busy

[Rohit Kulkarni]

Hi,

That worked for me too!

Thanks a lot Alex, Maciej!

-Rohit

On Sun, Jan 25, 2015 at 5:06 PM, Maciej Wasilak <wasilak@gmail.com> wrote:
> Hello,
>
> 2015-01-23 8:59 GMT+01:00 Alexander Aring <alex.aring@gmail.com>:
>>> Do you are sure that there is no daemon running or something else which
>>> automatically ifup the interface again if you want to set it down? Maybe
>>> just mv the /etc/$NETWORKING_STUFF into a separate directory and try again.
>
> After your pointers I've found the answer on one of the forums - the
> problem is caused by ifplugd service, which automatically brings up
> wpan0 interface after it is brought down.
> It seems that in previous branch (linux-wpan-next) this problem didn't
> exist, because wpan0 interface had to be manually created (and ifplugd
> didn't mess with it).
>
> Solution 1 (blunt): killall ifplugd
>
> Solution 2: edit /etc/default/ifplugd
>
> My working /etc/default/ifplugd below:
> ____
>
> # This file may be changed either manually or by running dpkg-reconfigure.
> #
> # N.B.: dpkg-reconfigure deletes everything from this file except for
> # the assignments to variables INTERFACES, HOTPLUG_INTERFACES, ARGS and
> # SUSPEND_ACTION.  When run it uses the current values of those variables
> # as their default values, thus preserving the administrator's changes.
> #
> # This file is sourced by both the init script /etc/init.d/ifplugd and
> # the udev script /lib/udev/ifplugd.agent to give default values.
> # The init script starts ifplugd for all interfaces listed in
> # INTERFACES, and the udev script starts ifplugd for all interfaces
> # listed in HOTPLUG_INTERFACES. The special value all starts one
> # ifplugd for all interfaces being present.
> INTERFACES="eth0"
> HOTPLUG_INTERFACES="eth0"
> ARGS="-q -f -u0 -d10 -w -I"
> SUSPEND_ACTION="stop"
>
> Thank you very much for your help!!!
>
> Regards
> Maciek