TeamForge : Post

Forum Topic - etfsctl.. what's expected behavior?: (3 Items)

View: as

Marc Roessler

04/03/2009 8:10 AM

post25958

etfsctl.. what's expected behavior?

Hi,

some problems with etfsctl turned up.. we are running on 2K Nand flash, so the driver is a patched version.

I'm starting ther etfs driver:
    fs-etfs-mpc8313erdb512 -D cs=0 -r 143360

It seems to be up and runnign:
# ls -l /dev/etfs2
brw-------  1 root      0            0,   0 Jan 01 02:15 /dev/etfs2

# etfsctl -d /dev/etfs2 -S -f -c
Error status on option 'S' : No such device

Before I start diving into all the etfslib the code: what's the problem here? /dev/etfs2 seems to be available..?

Greetings,
 Marc

Marc Roessler

04/03/2009 9:36 AM

post25963

Re: etfsctl.. what's expected behavior?

OK, for the record, found it after diving into the etfslib code:
it seems you HAVE to specify a mount point with the "-m" option, regardless of what the use-page says. There is NO 
default mount path set.

David Sarrazin

04/06/2009 10:48 AM

post26070

Re: etfsctl.. what's expected behavior?

This was corrected in the 6.4.0 documentation.  Support was added to ETFS for dynamic mount()/umount().   At the same 
time, the automounting was removed, unless a mountpoint is provided via the -m command-line option.

And yes, a partition has to be mounted and running, otherwise you will get ENODEV from the etfsctl command.

Return