Busy error status write

The exact same test program works fine for me on a Pi 2:

pi@raspberrypi:~/onoff $ cat test.js 
var Gpio = require('onoff').Gpio;
var led4 = new Gpio(4, 'out');
blink(led4, 500);

function blink(led, period) {
    led.write(1, function () {
        setTimeout(function(){
            led.write(0);
        }, period);
    });
}

pi@raspberrypi:~/onoff $ node test.js 
pi@raspberrypi:~/onoff $ node test.js 
pi@raspberrypi:~/onoff $ node test.js 
pi@raspberrypi:~/onoff $ node test.js 
pi@raspberrypi:~/onoff $ ls /sys/class/gpio/
export  gpio4  gpiochip0  unexport
pi@raspberrypi:~/onoff $ node test.js 
pi@raspberrypi:~/onoff $ node test.js 
pi@raspberrypi:~/onoff $ node test.js 
pi@raspberrypi:~/onoff $ ls /sys/class/gpio/
export  gpio4  gpiochip0  unexport
pi@raspberrypi:~/onoff $ node test.js 
pi@raspberrypi:~/onoff $ 

As can be seen, the test program can be called multiple times without issue.

This indicates that GPIO4 on your system is being reserved by some other software and is therefore not available for usage in the test program that turns the LED on and off. This can happen when device tree overlays are loaded. For example, if the device tree overlay w1-gpio-overlay.dtb is loaded by adding the following line to /boot/config.txt

device_tree_overlay=overlays/w1-gpio-overlay.dtb

then GPIO4 will be reserved for 1-Wire devices. Running the test program will then result in the following output (which is exactly what you’re seeing):

pi@raspberrypi:~/onoff $ cat test.js 
var Gpio = require('onoff').Gpio;
var led4 = new Gpio(4, 'out');
blink(led4, 500);

function blink(led, period) {
    led.write(1, function () {
        setTimeout(function(){
            led.write(0);
        }, period);
    });
}

pi@raspberrypi:~/onoff $ node test.js 
fs.js:706
    return binding.writeBuffer(fd, buffer, offset, length, position);
                   ^

Error: EBUSY: resource busy or locked, write
    at Error (native)
    at Object.fs.writeSync (fs.js:706:20)
    at Object.fs.writeFileSync (fs.js:1234:24)
    at new Gpio (/home/pi/onoff/node_modules/onoff/onoff.js:82:8)
    at Object.<anonymous> (/home/pi/onoff/test.js:2:12)
    at Module._compile (module.js:413:34)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Function.Module.runMain (module.js:447:10)
pi@raspberrypi:~/onoff $ 

Is there something running on your Pi 2 that is reserving GPIO4? For example, is a device tree overlay being loaded and reserving GPIO4?

bonding – write error – device or resource busy – operation not permitted

Recently, there was a little bit of confusion when following the article about activating network bonding without ifenslave – How to enable Linux bonding without ifenslave. At first, there were couple of errors:

Or similar error when changing the bonding mode:

The server just booted in rescue live cd and there is no active network configuration:

SCREENSHOT 1) Apparently, the /sys/class/net/bond0/bonding/mode and /sys/class/net/bond0/bonding/slaves are in read only state.

No writes means no new configuration could be installed and the bonding cannot be configured (reconfigured).
device or resource busy – operation not permitted

Bonding mode could be changed only when the bonding device is in DOWN state.

Network interfaces could be added to the boding device only if they were in DOWN state, too.

In addition, changing bonding mode could only happen if there were no network interfaces added to the bonding interface.

So if you intend to configure the bonding network device using /sys file system make sure all network devices you are going to use are in DOWN state. Even the network devices do not have IP (or it may be an IP from 169.254.0.0/16 – a random IP from 169.254.0.0/16 after a DHCP failed configuration) they may be in UP state! You may use IP or/and ifconfig commands to set the state of the interface or the interface’s link into DOWN state.
Many Linux distributions and live CDs use DHCP by default for all discovered wired network interfaces and it is typical to boot into a live cd and the bonding interface or the network interfaces to be in UP state.

There are also errors in dmesg (always check dmesg when receiving errors from tools for system configuration!), which are much more informative (for the bond device):

Set the DOWN state to the network devices using IP (from iproute2)

Replace the names (bond0, eth0, eth2) with those in your server accordingly.

Set the DOWN state to the network devices using ifconfig

Replace the names (bond0, eth0, eth2) with those in your server accrodingly.

Here is the our example from a Gentoo Live CD.

SCREENSHOT 2) Despite there si no IP set for bond0 the device is in UP state.

The interfaces enp129s0f0 and enp129s0f1 are UP with IPs from the network 169.254.0.0/16, which is not a real one.

SCREENSHOT 3) No matter which tool we use the ip (iproute2) or the old school one ifconfig to set the network interface in DOWN state.

As soon as you set the DOWN you can use /sys file system to set modes and the slaves.

SCREENSHOT 4) Even we have set the bonding interface in DOWN state we still cannot change the mode, because we included two network interfaces in the bonding group above.

To change the bonding mode the bonding device must be in DOWN state and no slaves devices to exist in it. Set the boding state in DOWN. Because we added the two network interfaces before, now we must remove them from the group and then change the boding mode to LACP. Now you can add the IP and set the link to UP (mind the right syntax!).

Leave a Reply Cancel reply

Find Us

Address
101010010100 Main Street
Earth, EA 101010101010100

E-mail
info@ahelpme.com

Hours (in the TimeBank)
1000000:00:0:00:00 in time…

About This Site

Highly skilled hominins inhabited planet Earth a long long ago! And these hominins have a need to share some knowledge here.

Источник

Ошибка device or resource busy

Часто при работе с флешками, дисками, образами или другими подобными объектами может возникать ошибка device or resource busy. Она может выводится, когда вы пытаетесь отмонтировать внешний диск, раздел, а также при попытке переместить или удалить файл.

В этой небольшой статье мы рассмотрим, почему может возникать данная ошибка, а также пути её устранения. Конечно, в случае с флешкой вы можете просто вынуть её из компьютера, но это не решение, потому что высока вероятность потерять не сохранённые данные. Есть пути обхода этой проблемы.

Что означает «device or resource busy»?

Если переводить дословно с английского, то это сообщение означает, что устройство или ресурс занято. Если объяснять более подробно — файл, который вы пытаетесь удалить или диск, который нужно отмонтировать, ещё используется одной из запущенных программ.

Это могло произойти потому, что программа ещё не завершила свою работу, зависла, возникли какие-либо проблемы в процессе её работы. Это актуально как для файлов, так и для съёмных носителей.

Как исправить device or resource busy?

Самое первое, что можно посоветовать — закрыть программы, которые могут использовать этот файл или один из файлов на съёмном носителе. Например, если сейчас воспроизводится один из видеофайлов, то проигрыватель надо закрыть. И только поле этого пробовать ещё раз выполнять операции.

Если вы не знаете какая программа мешает вам выполнить операцию, то это можно очень просто узнать с помощью команды lsof. Просто выполните её и отсейте только те записи, которые относятся к точке монтирования вашего носителя:

lsof | grep /media/sergiy/83AE-2346

Чтобы отсеять нужные процессы в самой утилите, используйте опцию +D, так даже лучше, потому что она не будет показывать системные службы, а отобразит только программу, которую надо завершить:

lsof +D /media/sergiy/83AE-2346

Теперь вы можете видеть все процессы, которые используют файлы на нашем носителе, и завершить их с помощью команды kill. В нашем случае надо завершить плеер totem с PID 5616:

Также, чтобы посмотреть, какие процессы используют файл, можно использовать команду fuser:

fuser -vm /home/sergiy/83AE-2346

Здесь вы тоже увидите всю необходимую информацию: будет отображаться пользователь, от имени которого запущен процесс. Точно так же можно его завершить:

Если вы закрыли все программы, но это не помогло, можно попытаться очистить файловый кэш системы с помощью такой команды:

sync && echo 2 > /proc/sys/vm/drop_caches

Выводы

В этой небольшой статье мы рассмотрели, как бороться с ошибкой device or resource busy Linux. Как видите, её очень просто исправить, даже если по началу кажется, что совсем непонятно, что можно сделать.

Источник

ODROID

[Solved]GPIO-bash: echo: write error: Device resource busy

[Solved]GPIO-bash: echo: write error: Device resource busy

Post by stool » Fri Apr 17, 2015 6:36 am

I am trying to follow the tutorial on http://odroid.com/dokuwiki/doku.php?id= . ent_gpio30 but when i type

echo 29 > /sys/class/gpio/export

I get bash: echo: write error: Device or resource busy
Then of course I can’t use the GPIO.

I have XU3 with Lubuntu 14.04 with the latest kernel and expansion board..
What am I missing ?
Thank you!

Re: GPIO — bash: echo: write error: Device or resource busy

Post by odroid » Fri Apr 17, 2015 1:59 pm

Re: GPIO — bash: echo: write error: Device or resource busy

Post by stool » Sat Apr 18, 2015 4:28 pm

Thank you for the prompt response!

Although I added

blacklist ioboard_bh1780
blacklist ioboard_bmp180
blacklist ioboard_keyled

in /etc/modprobe.d/blacklist.conf i get the same error «device or resources busy» when i try

odroid@odroid:/sys/devices/ioboard_key_led.12/driver$ echo 31 > /sys/class/gpio/export
-bash: echo: write error: Device or resource busy
odroid@odroid:/sys/devices/ioboard_key_led.12/driver$ echo 29 > /sys/class/gpio/export
-bash: echo: write error: Device or resource busy

In addition if i type lsmod i get :

Module Size Used by
8192cu 535333 0
bnep 10880 2
rfcomm 33099 0
bluetooth 231852 10 bnep,rfcomm
rfkill 12888 3 bluetooth
spidev 5889 0
nls_cp437 5128 1
vfat 9634 1
fat 53823 1 vfat
fuse 75218 2

So I am thinking that probably the ioboard drivers are not loaded

Источник

ls: write error: Device or resource busy #28

When i try to run pi_startup.sh i get a error:

The text was updated successfully, but these errors were encountered:

Same here.
I figure it’s about the line ls /sys/class/udc > UDC . Before running the script the file /sys/kernel/config/usb_gadget/poisontap/UDC doesn’t exist. Afterwards it does. I don’t have a clue why the script can create it, but can’t write to it.

Did you follow the installation instructions in README.md?

Yes i followed the installation instructions at the bottom of readme.md

So you’re saying pi_startup.sh is already in /etc/rc.local per the instructions, but you’re running it a second time as demonstrated in your screenshot? You should only run it once.

I followed everything but the addition to rc.local so I could see possible errors when running it manually — as it doesn’t work.

It seems to be the same error when the script is executed in rc.local because after booting /sys/kernel/config/usb_gadget/poisontap/UDC exists but is empty.

It partially works on my ubuntu computer, it only runs when i type 1.0.0.1 in the browser and not all requests are made to the pi zero.
Also windows doesn’t recognize the pi as a network adapter.

Why did you use a 128.0.0.0 subnet and not a 0.0.0.0 subnet?

What version of Windows?

128.0.0.0 works on every OS I tested where 0.0.0.0 doesn’t. I do want to update dhcpd.conf to use a short lease time, and have the subnet dynamically switch between the lower half and upper half of the IPv4 space but haven’t had a chance to, where the usb0 interface will hold an IP in both halves.

I am using windows 10.
And is it possible to emulate multiple lan adapters?

Источник

write: /sys/class/gpio/export: device or resource busy #30

I am trying to get simple gpio working on my rpi model B.

From the gopath/src/github.com/kidoman/embd/samples directory I run go build gpio.go and sudo ./gpio .

I get quick panic with panic: write: /sys/class/gpio/export: device or resource busy

Running latest raspbian image. I have built go from source on the device.

The text was updated successfully, but these errors were encountered:

Can you try with sudo ?

I can reproduce that with this code and before finish, I do Ctrl + c.

When I run again:

somehow restarting fixed my problem. I was also mucking about in raspi-config too, so not sure if anything there helped.

I think if I exit without closing down gpio it can leave stuff around that is hard to clean up. I can catch interrupts and execute a close before exiting, but I am not sure it is a good idea for anything outside of main to do this.

Two options:
1)
root@raspberrypi:

# echo 10 > /sys/class/gpio/unexport

You have to handle the signal in a goroutine and then switch on it in a loop, making the program exit cleanly and run it’s defer’s.

I ran into this same issue on a Raspberry Pi 2 Model B. Following @akofoed’s instructions, I was able to get the program to run multiple times in a row without any more errors:

What do you think about a PR to add this cleanup to the Raspberry Pi examples (including the readme)? That, or this should be handled automatically by the cleanup/ Close() functions for either the GPIO or the pin. Are there cases where people don’t want those pins to be cleaned up after the program exits?

Источник

Trying to run a Nodejs app to test Raspberry 3 B + Gpio Onoff Module but when i am trying to run the app getting this Error

fs.js:114
throw err;

Error: EBUSY: resource busy or locked, write
at Object.writeSync (fs.js:568:3)
at Object.writeFileSync (fs.js:1199:26)
at new Gpio (/home/pi/Desktop/pitesting/node_modules/onoff/onoff.js:96:10)
at Object.<anonymous> (/home/pi/Desktop/pitesting/blink.js:3:7)
at Module._compile (internal/modules/cjs/loader.js:701:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:712:10)
at Module.load (internal/modules/cjs/loader.js:600:32)
at tryModuleLoad (internal/modules/cjs/loader.js:539:12)
at Function.Module._load (internal/modules/cjs/loader.js:531:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:754:12)

Here is my App Code

var onoff = require('onoff');
var Gpio = onoff.Gpio,
  led = new Gpio(4, 'out'),
  interval;
interval = setInterval(function () {
  var value = (led.readSync() + 1) % 2;
  led.write(value, function () {
    console.log("Changed LED state to: " + value);
  });
}, 2000);
process.on('SIGINT', function () {
  clearInterval(interval);
  led.writeSync(0);
  led.unexport();
  console.log('Bye, bye!');
  process.exit();
});

Already Tried Fixes by updating and upgrading apt and reinstalling node modules.

Please Help me to resolve this issue.