Forum Topic - fs-qnx6 mounting from mkifs build file: (4 Items)
   
fs-qnx6 mounting from mkifs build file  
I have problem with mounting fs-qnx6.so (6.4) from boot image file.

I have AFAYA (micro disk module) 1Gb flash with IDE interface.
In the "image.build" file for mkifs , using next cmd's:

devb-eide blk automount=hd0t179:/:qnx6 &   ---> error

I'm try to use other cmd's:

devb-eide blk &
waitfor /dev/hd0t179
mount -t qnx6 /dev/hd0t179 /             ---> error too


ls -l /dev/hd0 -- ok
ls -l /dev/hd0t179  -- ok
but :
mount -t qnx6 /dev/hd0t179 /hd
show:
mount: Can't mount /hd (type qnx6)
mount: Possible reason: Read-only file system   ?????!!!

IDE created with:

fdisk /dev/hd0 destroy -a
fdisk /dev/hd0 add -t179
fdisk /dev/hd0 boot -t179
fdisk /dev/hd0 loader
mount -e /dev/hd0
mkqnx6fs -q -Tdesktop /dev/hd0t179


Please help me.
SNS





Re: fs-qnx6 mounting from mkifs build file  
Sergey,

What is the output of sloginfo?

The compact flash device may not support the sync command.  If this is the case add "sync=ignore" to the command-line

devb-eide blk qnx6 sync=ignore

If the hardware does not support the sync command, then fs-qnx6 cannot promise that all data is completely written to 
the storage media (it might be in the controller's buffer).

http://www.qnx.com/developers/docs/6.4.0/neutrino/utilities/f/fs-qnx6.so.html


As another test, are you able to mount read-only?
RE: fs-qnx6 mounting from mkifs build file  

> -----Original Message-----
> From: David Sarrazin [mailto:community-noreply@qnx.com]
> Sent: February-09-09 4:34 PM
> To: general-filesystems
> Subject: Re: fs-qnx6 mounting from mkifs build file
> 
> Sergey,
> 
> What is the output of sloginfo?
> 
> The compact flash device may not support the sync command.  If this is
> the case add "sync=ignore" to the command-line
> 

Could this explain why some model of SSD seems to "forget" everything that was written to them after a reboot.  To solve
 that problem one manufacturer gave us an application to change a setting in the device and it started to work properly.
  I wasn`t involved so I don`t have any details but we were told the problem was caused by the QNX driver doing thing "
differently".

When I saw this post I got me to think maybe sync=ignore would be a work around for that problem?


> devb-eide blk qnx6 sync=ignore
> 
> If the hardware does not support the sync command, then fs-qnx6 cannot
> promise that all data is completely written to the storage media (it
> might be in the controller's buffer).
> 
> http://www.qnx.com/developers/docs/6.4.0/neutrino/utilities/f/fs-
> qnx6.so.html
> 
> 
> As another test, are you able to mount read-only?
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post21835
> 
Re: RE: fs-qnx6 mounting from mkifs build file  
> > The compact flash device may not support the sync command.  If this is
> > the case add "sync=ignore" to the command-line

You probably don't mean this.  "ignore" will not only not SC_SYNC but will also not drain dirty blocks from the io-blk 
cache (if delwri != 0).  It is intended for use with a UPS where you can cleanly unmount; in all other cases it will 
almost certainly lead to lost data.  "sync=optional" is the relevant option here; this will try SC_SYNC but won't get 
upset if this is unsupported (the onus is on you as the user of that option to know the h/w does not need this).

p.s. yes, the docs were wrong, they've been corrected and now read:
"
sync=mode
    Specify the required disk synchronization capability. The mode mode must be one of the following:

        * mandatory (the default) — the drive must support synchronisation to allow a filesystem to be mounted read/
write. If it doesn't, the mount fails and returns EROFS. A read-only mount (mount -r) can always be performed on any 
device.
        * optional — attempt synchronization, but ignore any error if the drive doesn't support such an operation. The 
driver might be incorrectly advertising the capabilities, or the physical media might not require explicit 
synchronization (write-through).
        * ignore — never issue a sychronization command to the disk, and don't drain dirty blocks from the fileystem 
cache (until an explicit umount). This mode is suitable only for use with a UPS.
"