http://community.qnx.com/sf/discussion/do/listTopics/projects.filesystems/discussion.general Posts for General http://community.qnx.com/sf/go/post101322 hello i have some problem. in harman&decker cic for bmw x1. i can mount this partitions, but in fdisk i see only extendet part. how i can recreate 5 77 partition in fdisk ? (qnx6.5) Mon, 13 May 2013 08:38:54 GMT http://community.qnx.com/sf/go/post101322 Dmitriy Dupliy 2013-05-13T08:38:54Z http://community.qnx.com/sf/go/post101321 > Ok, I finally found it out. I rebooted the whole system and was able to mount > everything. May be there was a lock put on a file somewhere. > Thanks, > David. > > Le 31.05.2012 17:03, David Billard a écrit : > > Ok, I found the "mount -t qnx6". Now I have a mounting problem. I can mount > the > > partitions: > > /dev/hd0t77.1 > > /dev/hd0t77.2 > > /dev/hd0t77.3 > > /dev/hd0t77.4 > > /dev/hd0t77.5 > > > > But not the /dev/hd0t77 (which is the biggest partition but the numbering > scheme > > suggests that this partition is subdivided in 1 to 5 sub partitions). Does > it > > means that there is an unpartitionned (and unformatted) space on the drive? > > > > Many thanks, > > > > David. > > Le 31.05.2012 16:37, David Billard a écrit : > >> Hi David, > >> > >> Sorry to bother you with my problem. How can I mount a qnx6 file system > (I'm > >> using the boot CD)? > >> > >> Many thanks, > >> > >> David. > >> > >> Le 15.05.2012 16:35, David Sarrazin a écrit : > >>> What OS version are you running? Partition type 77 is normally reserved > for partitions of type QNX4. Fdisk should say "QNX4" , simply because the > type is 77. You can also try chkqnx6fs, on the off chance that the disks are > formatted with the QNX6 file system. > >>> > >>> David > >>> > >>>> -----Original Message----- > >>>> From: David Billard [mailto:community-noreply@qnx.com] > >>>> Sent: May-15-12 10:33 AM > >>>> To: general-filesystems@community.qnx.com > >>>> Subject: Re: Mounting qnx4 fs with errors > >>>> > >>>> Hi David, > >>>> > >>>> it says that my partition is not a QNX4 fs. A rapid view with fdisk says > >>>> "unknown loader". Is there any way to detect which fs is on the > partitions > >>>> (I'm almost sure it's qnx4, but perhaps am i wrong). > >>>> > >>>> many thanks, > >>>> > >>>> David. > >>>> > >>>> Le 15.05.2012 16:21, David Sarrazin a écrit : > >>>>> First thing to try is chkfsys, which is the QNX4 file system checker > tool. If > >>>> you don't want to make any changes to the disk, the -f option will > prevent > >>>> the tool from modifying anything. > >>>>> > >>>>>> -----Original Message----- > >>>>>> From: David Billard [mailto:community-noreply@qnx.com] > >>>>>> Sent: May-15-12 10:35 AM > >>>>>> To: general-filesystems > >>>>>> Subject: Mounting qnx4 fs with errors > >>>>>> > >>>>>> Dear all, > >>>>>> > >>>>>> I'm new to QNX. I would like to recover files from a qnx4 filesystem > >>>>>> on a harddrive. The hardrive has 6 partitions. I used the BOOT-CD and > >>>>>> the photon file manager. If I do a df, it sees : > >>>>>> > >>>>>> /dev/hd0 > >>>>>> /dev/hd0t77 > >>>>>> /dev/hd0t77.1 > >>>>>> /dev/hd0t77.2 > >>>>>> /dev/hd0t77.3 > >>>>>> /dev/hd0t77.4 > >>>>>> /dev/hd0t77.5 > >>>>>> > >>>>>> If I try to mount /dev/hd0t77 or any of its declination, it says that > >>>>>> the fs is corrupted. > >>>>>> > >>>>>> To my knowledge, the disk is not damaged. Do you see any reason for > >>>>>> this message or any solution for me? > >>>>>> > >>>>>> Is there a way to fix the fs? > >>>>>> > >>>>>> Many thanks, > >>>>>> > >>>>>> david. > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> _______________________________________________ > >>>>>> > >>>>>> General > >>>>>> http://community.qnx.com/sf/go/post93087 > >>>>>> To cancel your subscription to this discussion, please e-mail > >>>>>> general- filesystems-unsubscribe@community.qnx.com > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> > >>>>> General > >>>>> http://community.qnx.com/sf/go/post93088 > >>>>> To cancel your subscription to this discussion, please e-mail > >>>>> general-filesystems-unsubscribe@community.qnx.com > >>>> > >>>> -- > >>>> Prof. David Billard | David.Billard@hesge.ch > >>>> University of Applied Sciences in Geneva | tel: +41 22 388 1885 > >>>> Bât. F, 7 route de Drize - CH-1227 Carouge | fax: +41 22 388 1701 > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> > >>>> General > >>>> http://community.qnx.com/sf/go/post93090 > >>>> To cancel your subscription to this discussion, please e-mail general- > >>>> filesystems-unsubscribe@community.qnx.com > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> > >>> General > >>> http://community.qnx.com/sf/go/post93091 > >>> To cancel your subscription to this discussion, please e-mail general- > filesystems-unsubscribe@community.qnx.com > >> > > > > -- > Prof. David Billard | David.Billard@hesge.ch > University of Applied Sciences in Geneva | tel: +41 22 388 1885 > Bât. F, 7 route de Drize - CH-1227 Carouge | fax: +41 22 388 1701 > Mon, 13 May 2013 08:37:57 GMT http://community.qnx.com/sf/go/post101321 Dmitriy Dupliy 2013-05-13T08:37:57Z http://community.qnx.com/sf/go/post101310 Now with what is presumably the correct command: # mount -text2 /dev/umass0t131 /fs/T1 mount: Can't mount /fs/T1 (type ext2) mount: Possible reason: Corrupted file system detected Did the ext2 format outpace fs-ext2.so? Fri, 10 May 2013 18:53:02 GMT http://community.qnx.com/sf/go/post101310 Norton Allen 2013-05-10T18:53:02Z http://community.qnx.com/sf/go/post101308 I am trying to figure out the fastest way to get data off of our embedded system post-flight and into the hands of the scientists for data analysis. We expect to be acquiring ~40GB per flight, and it needs to get to three different systems running both Linux and Windows for data analysis. Having done the math, I figured the fastest method would be to use eSATA to write to an external disk, then move the disk to the first target system and repeat 3 times. Looking at the matrix of supported filesystems, it looks like ext2 is the only one that is both writable under QNX and readable under both Linux and Windows. I've got the drive, I formatted it with ext2 on a CentOS 6.4 system, brought it over to QNX, see that the partition shows up (/dev/umass0t131), but: # mount -T ext2 /dev/umass0t131 /fs/T1 mount: Can't mount /fs/T1 (type ext2) mount: Possible reason: Invalid argument Any ideas what's going on? Any suggestions? Fri, 10 May 2013 17:36:12 GMT http://community.qnx.com/sf/go/post101308 Norton Allen 2013-05-10T17:36:12Z http://community.qnx.com/sf/go/post101216 Thank you very much. I really appreciate your help. 于 2013/5/7 21:18, Chris Travis 写道: > Sorry, but this has Restricted Source Access, so if you are a customer or a partner of QNX Software Systems and need access to QNX proprietary source code in this project please contact your QSS Sales or Support representative. > > Unless somebody has some code they can share with you for storage info. > > -----Original Message----- > From: Chris Travis > Sent: May-07-13 9:07 AM > To: 'general-filesystems@community.qnx.com' > Subject: RE: How to get storage and memory information? > > Actually you wouldn't have access to this source link...this might be available on foundry27 for you...let me look. > > -----Original Message----- > From: Chris Travis > Sent: May-07-13 9:05 AM > To: general-filesystems > Subject: RE: How to get storage and memory information? > > You could have a look at the df source for disk space: > http://svn.ott.qnx.com/view/product/trunk/utils/d/df/nto/ > > Below is some C code for getting free and total memory. > > Chris > > #include <errno.h> > #include <stdint.h> > #include <unistd.h> > #include <stdarg.h> > #include <stdlib.h> > #include <stdio.h> > #include <string.h> > #include <sys/stat.h> > #include <sys/mman.h> > #include <sys/syspage.h> > > uint64_t > get_free_mem (void) > { > int ret; > struct stat64 sbuf; > ret = stat64("/proc", &sbuf); > if (ret == -1) { > printf("stat(/proc) failed: %s", strerror(errno)); > } > return sbuf.st_size; > } > > uint64_t > get_total_mem (void) > { > char *str = SYSPAGE_ENTRY(strings)->data; > struct asinfo_entry *as = SYSPAGE_ENTRY(asinfo); > uint64_t total = 0; > unsigned num; > > for (num = _syspage_ptr->asinfo.entry_size / sizeof(*as); num > 0; --num) { > if(strcmp(&str[as->name], "ram") == 0) { > total += as->end - as->start + 1; > } > ++as; > } > return total; > } > > int main (int argc, char **argv) > { > uint64_t free_mem = get_free_mem(); > uint64_t total_mem = get_total_mem(); > > printf("FreeMem/TotalMem: %llu/%llu",free_mem,total_mem ); } > > -----Original Message----- > From: Allen Chen [mailto:community-noreply@qnx.com] > Sent: May-07-13 3:29 AM > To: general-filesystems > Subject: How to get storage and memory information? > > I want to implement a program in C++ to get system storage information, such as total storage size, free storage size, total memory size and free memory size. > How to do it? > > Allen Chen > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post101198 > To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post101215 > To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com > Tue, 07 May 2013 13:22:41 GMT http://community.qnx.com/sf/go/post101216 Allen Chen 2013-05-07T13:22:41Z http://community.qnx.com/sf/go/post101215 Sorry, but this has Restricted Source Access, so if you are a customer or a partner of QNX Software Systems and need access to QNX proprietary source code in this project please contact your QSS Sales or Support representative. Unless somebody has some code they can share with you for storage info. -----Original Message----- From: Chris Travis Sent: May-07-13 9:07 AM To: 'general-filesystems@community.qnx.com' Subject: RE: How to get storage and memory information? Actually you wouldn't have access to this source link...this might be available on foundry27 for you...let me look. -----Original Message----- From: Chris Travis Sent: May-07-13 9:05 AM To: general-filesystems Subject: RE: How to get storage and memory information? You could have a look at the df source for disk space: http://svn.ott.qnx.com/view/product/trunk/utils/d/df/nto/ Below is some C code for getting free and total memory. Chris #include <errno.h> #include <stdint.h> #include <unistd.h> #include <stdarg.h> #include <stdlib.h> #include <stdio.h> #include <string.h> #include <sys/stat.h> #include <sys/mman.h> #include <sys/syspage.h> uint64_t get_free_mem (void) { int ret; struct stat64 sbuf; ret = stat64("/proc", &sbuf); if (ret == -1) { printf("stat(/proc) failed: %s", strerror(errno)); } return sbuf.st_size; } uint64_t get_total_mem (void) { char *str = SYSPAGE_ENTRY(strings)->data; struct asinfo_entry *as = SYSPAGE_ENTRY(asinfo); uint64_t total = 0; unsigned num; for (num = _syspage_ptr->asinfo.entry_size / sizeof(*as); num > 0; --num) { if(strcmp(&str[as->name], "ram") == 0) { total += as->end - as->start + 1; } ++as; } return total; } int main (int argc, char **argv) { uint64_t free_mem = get_free_mem(); uint64_t total_mem = get_total_mem(); printf("FreeMem/TotalMem: %llu/%llu",free_mem,total_mem ); } -----Original Message----- From: Allen Chen [mailto:community-noreply@qnx.com] Sent: May-07-13 3:29 AM To: general-filesystems Subject: How to get storage and memory information? I want to implement a program in C++ to get system storage information, such as total storage size, free storage size, total memory size and free memory size. How to do it? Allen Chen _______________________________________________ General http://community.qnx.com/sf/go/post101198 To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com Tue, 07 May 2013 13:18:48 GMT http://community.qnx.com/sf/go/post101215 Chris Travis 2013-05-07T13:18:48Z http://community.qnx.com/sf/go/post101213 Actually you wouldn't have access to this source link...this might be available on foundry27 for you...let me look. -----Original Message----- From: Chris Travis Sent: May-07-13 9:05 AM To: general-filesystems Subject: RE: How to get storage and memory information? You could have a look at the df source for disk space: http://svn.ott.qnx.com/view/product/trunk/utils/d/df/nto/ Below is some C code for getting free and total memory. Chris #include <errno.h> #include <stdint.h> #include <unistd.h> #include <stdarg.h> #include <stdlib.h> #include <stdio.h> #include <string.h> #include <sys/stat.h> #include <sys/mman.h> #include <sys/syspage.h> uint64_t get_free_mem (void) { int ret; struct stat64 sbuf; ret = stat64("/proc", &sbuf); if (ret == -1) { printf("stat(/proc) failed: %s", strerror(errno)); } return sbuf.st_size; } uint64_t get_total_mem (void) { char *str = SYSPAGE_ENTRY(strings)->data; struct asinfo_entry *as = SYSPAGE_ENTRY(asinfo); uint64_t total = 0; unsigned num; for (num = _syspage_ptr->asinfo.entry_size / sizeof(*as); num > 0; --num) { if(strcmp(&str[as->name], "ram") == 0) { total += as->end - as->start + 1; } ++as; } return total; } int main (int argc, char **argv) { uint64_t free_mem = get_free_mem(); uint64_t total_mem = get_total_mem(); printf("FreeMem/TotalMem: %llu/%llu",free_mem,total_mem ); } -----Original Message----- From: Allen Chen [mailto:community-noreply@qnx.com] Sent: May-07-13 3:29 AM To: general-filesystems Subject: How to get storage and memory information? I want to implement a program in C++ to get system storage information, such as total storage size, free storage size, total memory size and free memory size. How to do it? Allen Chen _______________________________________________ General http://community.qnx.com/sf/go/post101198 To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com Tue, 07 May 2013 13:07:01 GMT http://community.qnx.com/sf/go/post101213 Chris Travis 2013-05-07T13:07:01Z http://community.qnx.com/sf/go/post101212 You could have a look at the df source for disk space: http://svn.ott.qnx.com/view/product/trunk/utils/d/df/nto/ Below is some C code for getting free and total memory. Chris #include <errno.h> #include <stdint.h> #include <unistd.h> #include <stdarg.h> #include <stdlib.h> #include <stdio.h> #include <string.h> #include <sys/stat.h> #include <sys/mman.h> #include <sys/syspage.h> uint64_t get_free_mem (void) { int ret; struct stat64 sbuf; ret = stat64("/proc", &sbuf); if (ret == -1) { printf("stat(/proc) failed: %s", strerror(errno)); } return sbuf.st_size; } uint64_t get_total_mem (void) { char *str = SYSPAGE_ENTRY(strings)->data; struct asinfo_entry *as = SYSPAGE_ENTRY(asinfo); uint64_t total = 0; unsigned num; for (num = _syspage_ptr->asinfo.entry_size / sizeof(*as); num > 0; --num) { if(strcmp(&str[as->name], "ram") == 0) { total += as->end - as->start + 1; } ++as; } return total; } int main (int argc, char **argv) { uint64_t free_mem = get_free_mem(); uint64_t total_mem = get_total_mem(); printf("FreeMem/TotalMem: %llu/%llu",free_mem,total_mem ); } -----Original Message----- From: Allen Chen [mailto:community-noreply@qnx.com] Sent: May-07-13 3:29 AM To: general-filesystems Subject: How to get storage and memory information? I want to implement a program in C++ to get system storage information, such as total storage size, free storage size, total memory size and free memory size. How to do it? Allen Chen _______________________________________________ General http://community.qnx.com/sf/go/post101198 To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com Tue, 07 May 2013 13:05:34 GMT http://community.qnx.com/sf/go/post101212 Chris Travis 2013-05-07T13:05:34Z http://community.qnx.com/sf/go/post101198 I want to implement a program in C++ to get system storage information, such as total storage size, free storage size, total memory size and free memory size. How to do it? Allen Chen Tue, 07 May 2013 07:28:58 GMT http://community.qnx.com/sf/go/post101198 Allen Chen 2013-05-07T07:28:58Z http://community.qnx.com/sf/go/post100577 Hello Daniel Lee, I have the same problem. When I try to formate the flash the same error occur. Do you have any solution? Thank you! Kevin Mon, 15 Apr 2013 13:30:21 GMT http://community.qnx.com/sf/go/post100577 Kevin B. 2013-04-15T13:30:21Z http://community.qnx.com/sf/go/post100109 I am using a SILICON Systems 80 GB SSD. not being identified at boot up.. i get the following slogger errors. continously.. for days as the system was left in this state for a week. Reboot helps sometimes.. Will setting DRDY off help.. where can i get more info on the driver - device interactions ? using QNX6. 20130313_170922551_slog 3/13/2013 17:07 261 13 0 SLOG_ERROR eide_command: !DRDY: 0 20130313_170922551_slog 3/13/2013 17:07 261 13 0 SLOG_ERROR eide_dump_regs: error 0 status 0 20130313_170922551_slog 3/13/2013 17:07 261 13 0 SLOG_ERROR eide_command: !DRDY: 0 20130313_170922551_slog 3/13/2013 17:07 262 13 0 SLOG_ERROR eide_dump_regs: error 0 status 0 Fri, 22 Mar 2013 17:36:27 GMT http://community.qnx.com/sf/go/post100109 shubha devadatta 2013-03-22T17:36:27Z http://community.qnx.com/sf/go/post100010 If I use fdisk to create the partitions, the naming of them is not under my control. Fdisk decides that the second partition is hd0t179.1, only if I make the first and second partitions t179; however, documentation says that t177 is primary and t178 is secondary for QNX6, so why would it allow me to have two t179s? Tue, 19 Mar 2013 16:50:45 GMT http://community.qnx.com/sf/go/post100010 Derek McIntyre 2013-03-19T16:50:45Z http://community.qnx.com/sf/go/post100009 With t07? are of the type QNX4 filesystem ( compatible with QNX6 ), and t17? are of type QNX6. Check to doc about these filesystem to chose the one that best fits your need. I think the 4 partitions limit is that of a standard primary boot loader, some fancier boot loader can extend that though. I'm not sure if the QNX partition numbering is part of some standard. In theory you could use any number it doesn't really matter. All that matter is one partition be set as boot partition and that is it. The naming of the partition is totally under your control. However some tool like diskboot, used in the default startup sequence, may have some specific requirement, don't know about that. -----Message d'origine----- De : Derek McIntyre [mailto:community-noreply@qnx.com] Envoyé : Tuesday, March 19, 2013 11:38 AM À : general-filesystems Objet : FDisk - Partitioning multiple filesystems of the same type I'm finding a few discrepancies in QNX's documentation of partitioning and proper setup of multiple partitions of the same file system type, and was hoping someone could clarify for me. 1.) Primary t0177 and secondary t0178, or t0177 and t0177.1: which is correct? Several parts of the documentation, as well as other sites, mention that t077/t0177 are the primary partitions while t078/t0178 are secondary and t079/t0179 are tertiary for qnx4 and qnx6 respectively; however, fdisk will allow you to create multiple t0179 partitions and will label them as /dev/hd0t179 and /dev/hd0t179.1. Is the first correct? And if so, what is the reason for the second, or is it a mistake? 2.) Is there a limit of 4 partitions of the same file system on the same hard drive? The documentation mentions this rule, but there are only 3 file system numbers listed. This leads me to believe there is a 4th t080/t180 partition file system type: is that true? Any information would be appreciated. Thanks! _______________________________________________ General http://community.qnx.com/sf/go/post100005 To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com Tue, 19 Mar 2013 16:45:54 GMT http://community.qnx.com/sf/go/post100009 Mario Charest 2013-03-19T16:45:54Z http://community.qnx.com/sf/go/post100005 I'm finding a few discrepancies in QNX's documentation of partitioning and proper setup of multiple partitions of the same file system type, and was hoping someone could clarify for me. 1.) Primary t0177 and secondary t0178, or t0177 and t0177.1: which is correct? Several parts of the documentation, as well as other sites, mention that t077/t0177 are the primary partitions while t078/t0178 are secondary and t079/t0179 are tertiary for qnx4 and qnx6 respectively; however, fdisk will allow you to create multiple t0179 partitions and will label them as /dev/hd0t179 and /dev/hd0t179.1. Is the first correct? And if so, what is the reason for the second, or is it a mistake? 2.) Is there a limit of 4 partitions of the same file system on the same hard drive? The documentation mentions this rule, but there are only 3 file system numbers listed. This leads me to believe there is a 4th t080/t180 partition file system type: is that true? Any information would be appreciated. Thanks! Tue, 19 Mar 2013 15:37:42 GMT http://community.qnx.com/sf/go/post100005 Derek McIntyre 2013-03-19T15:37:42Z http://community.qnx.com/sf/go/post99755 Hi David, thanks for the input, so do you mean after mmap on a shm file and using the file fd directly or using the pointer returned by mmap doesnot give any performance benefit. Then why do we need to have mmap ? can the shm file fd be directly used for transfer without using mmap ? Fri, 08 Mar 2013 16:12:53 GMT http://community.qnx.com/sf/go/post99755 Balaaji Tirouvengadam 2013-03-08T16:12:53Z http://community.qnx.com/sf/go/post99744 Using the fd directly will perform a file operation, and not modify the mmap memory buffers. When the memory buffers are unmapped, their contents will overwrite whatever changes you made to the file. For this reason, you should only access the file via the mmap memory buffers OR through the fd, do not mix them. Your application will know better than the kernel when you are finished with a specific piece of buffer, so you application can make better decisions about when to flush the changes to disk. Other than this, I don't know if there is any performance penalty for using mmap versus reading the file directly. I would suggest though, if you are looking for performance, make sure you do NOT use fopen()/fread()/fwrite(), and do your file access in the largest possible buffer (32k or 64k read and write sizes offer good performance). David -----Original Message----- From: Balaaji Tirouvengadam [mailto:community-noreply@qnx.com] Sent: Thursday, March 07, 2013 1:59 PM To: general-filesystems Subject: Performing read operation on fd after mmap Hi, I am trying to find the performance difference between 1.) using the pointer returned by mmap() of shm_open() retruned fd 2.) shm_open(), call mmap(), ignore the pinter returned and just use the fd for data read/write operations. Does the both operation gives same performance results ? wehther the both does only memory operation instead of one memory and the other as file operation ? _______________________________________________ General http://community.qnx.com/sf/go/post99738 To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com Thu, 07 Mar 2013 22:37:35 GMT http://community.qnx.com/sf/go/post99744 David Sarrazin 2013-03-07T22:37:35Z http://community.qnx.com/sf/go/post99738 Hi, I am trying to find the performance difference between 1.) using the pointer returned by mmap() of shm_open() retruned fd 2.) shm_open(), call mmap(), ignore the pinter returned and just use the fd for data read/write operations. Does the both operation gives same performance results ? wehther the both does only memory operation instead of one memory and the other as file operation ? Thu, 07 Mar 2013 18:58:59 GMT http://community.qnx.com/sf/go/post99738 Balaaji Tirouvengadam 2013-03-07T18:58:59Z http://community.qnx.com/sf/go/post98638 Adding that file solved my problem. Of course I added a shadow file for password which was created in a writable file system. Thanks for your help. Regards Thu, 17 Jan 2013 17:08:37 GMT http://community.qnx.com/sf/go/post98638 enes aykurt 2013-01-17T17:08:37Z http://community.qnx.com/sf/go/post98591 Thanks for the reply David, the vast majority of the access to the files is with read() and write() after and open() call. Am I correct in assuming that when a file is open()ed by name it will always open the correct file regardless of the inode number ? Wed, 16 Jan 2013 09:40:07 GMT http://community.qnx.com/sf/go/post98591 Graham Watson 2013-01-16T09:40:07Z http://community.qnx.com/sf/go/post98580 Graham, If you are attempting to execute programs from this resmgr, then you'll need to ensure the inodes are unique, as the process manager uses the inode to identify open executable files. Similiarily, nfsd and fs-nfs3 rely on the inode number for caching reasons. It depends on what clients are accessing this resource manager, and what the client is doing with the inode number. David > -----Original Message----- > From: Watson, Graham [mailto:community-noreply@qnx.com] > Sent: January-15-13 11:10 AM > To: general-filesystems@community.qnx.com > Subject: RE: Effect of Duplicate inode numbers in resource managed files > > <BR> > <BR> > HI Mario > > Thanks for your reply, I understand was an inode is and have had a lot of > experience with UNIX filesystems. My question in more to do with the > implications of having duplicate inodes in systems out in the field and what > possible problems might arise. The systems we run control very heavy and > expensive equipment and I would not want anything going wrong and > someone possible getting hurt. If you can give me anymore info on what > possible side effects might occour I would be very grateful. > > Regards > > Graham Watson | Software Engineer > Waukesha Magnetic Bearings > Downlands Business Park, Lyons Way, Worthing West Sussex BN14 9LA > United Kingdom > Mobile: +44 (0)7762 541863 | Office: +44 (0)1903 275543 > gwatson@waukbearing.com www.waukbearing.com P  Please consider the > environment before you print. > > -----Original Message----- > From: Mario Beaulieu [mailto:community-noreply@qnx.com] > Sent: 15 January 2013 14:22 > To: general-filesystems > Subject: Re: Effect of Duplicate inode numbers in resource managed files > > The inode is a filesystem data structure that represents a file (its location on > disk, owner, permissions, etc). > If 2 "files" on the same partition have the same inode, they are actually 2 > names for the same file. > > You can create many names for the same file with the command "ln". > When you do "ls -l", the first value after the permissions is the number of > files pointing to that inode, or should I say, the number of filenames > corresponding to that file. > Below, I have created file "myfile" and the link number is 1. > After creating a second name for that same file with command "ln", we see > that the number of links is 2 for each of those: > > # echo "Hello" > myfile > # ls -l > total 1 > -rw-rw-r-- 1 root nto 6 Jan 15 09:07 myfile > # ln myfile AnotherLinkToMyFyle > # ls -l > total 2 > -rw-rw-r-- 2 root nto 6 Jan 15 09:07 AnotherLinkToMyFyle > -rw-rw-r-- 2 root nto 6 Jan 15 09:07 myfile > # echo "Hello again" > otherFile > # ls -l > total 3 > -rw-rw-r-- 2 root nto 6 Jan 15 09:07 AnotherLinkToMyFyle > -rw-rw-r-- 2 root nto 6 Jan 15 09:07 myfile > -rw-rw-r-- 1 root nto 12 Jan 15 09:12 otherFile > # > > See the inode number like the page number in a book. In addition to the > inode, you have to check the partition. Inodes on different partitions are > completely unrelated, like page numbers on 2 different books. > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post98567 > To cancel your subscription to this discussion, please e-mail general- > filesystems-unsubscribe@community.qnx.com > <font size="-1">Waukesha Bearings Limited is a limited company registered > in England and Wales.<BR> Registered number: 4203526. Registered office: > 53-55 The Broadway, Joel Street, Northwood, Middlesex, HA6 1NZ <BR> > > <font color="#A9A9A9">PLEASE NOTE! This message (and any associated > files) is intended only for the use of the individual or entity to which it is > addressed and may contain information that is confidential, subject to > copyright or constitutes a trade secret. If you are not the intended recipient > you are hereby notified that any dissemination, copying or distribution of this > message, or files associated with this message, is strictly prohibited. If you > have received this message in error, please notify us immediately by replying > to the message and deleting it from your computer. Messages sent to and > from us may be monitored. > > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post98577 > To cancel your subscription to this discussion, please e-mail general- > filesystems-unsubscribe@community.qnx.com Tue, 15 Jan 2013 16:29:40 GMT http://community.qnx.com/sf/go/post98580 David Sarrazin 2013-01-15T16:29:40Z http://community.qnx.com/sf/go/post98577 <BR> <BR> HI Mario Thanks for your reply, I understand was an inode is and have had a lot of experience with UNIX filesystems. My question in more to do with the implications of having duplicate inodes in systems out in the field and what possible problems might arise. The systems we run control very heavy and expensive equipment and I would not want anything going wrong and someone possible getting hurt. If you can give me anymore info on what possible side effects might occour I would be very grateful. Regards Graham Watson | Software Engineer Waukesha Magnetic Bearings Downlands Business Park, Lyons Way, Worthing West Sussex BN14 9LA United Kingdom Mobile: +44 (0)7762 541863 | Office: +44 (0)1903 275543 gwatson@waukbearing.com www.waukbearing.com   Please consider the environment before you print.   -----Original Message----- From: Mario Beaulieu [mailto:community-noreply@qnx.com] Sent: 15 January 2013 14:22 To: general-filesystems Subject: Re: Effect of Duplicate inode numbers in resource managed files The inode is a filesystem data structure that represents a file (its location on disk, owner, permissions, etc). If 2 "files" on the same partition have the same inode, they are actually 2 names for the same file. You can create many names for the same file with the command "ln". When you do "ls -l", the first value after the permissions is the number of files pointing to that inode, or should I say, the number of filenames corresponding to that file. Below, I have created file "myfile" and the link number is 1. After creating a second name for that same file with command "ln", we see that the number of links is 2 for each of those: # echo "Hello" > myfile # ls -l total 1 -rw-rw-r-- 1 root nto 6 Jan 15 09:07 myfile # ln myfile AnotherLinkToMyFyle # ls -l total 2 -rw-rw-r-- 2 root nto 6 Jan 15 09:07 AnotherLinkToMyFyle -rw-rw-r-- 2 root nto 6 Jan 15 09:07 myfile # echo "Hello again" > otherFile # ls -l total 3 -rw-rw-r-- 2 root nto 6 Jan 15 09:07 AnotherLinkToMyFyle -rw-rw-r-- 2 root nto 6 Jan 15 09:07 myfile -rw-rw-r-- 1 root nto 12 Jan 15 09:12 otherFile # See the inode number like the page number in a book. In addition to the inode, you have to check the partition. Inodes on different partitions are completely unrelated, like page numbers on 2 different books. _______________________________________________ General http://community.qnx.com/sf/go/post98567 To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com <font size="-1">Waukesha Bearings Limited is a limited company registered in England and Wales.<BR> Registered number: 4203526. Registered office: 53-55 The Broadway, Joel Street, Northwood, Middlesex, HA6 1NZ <BR> <font color="#A9A9A9">PLEASE NOTE! This message (and any associated files) is intended only for the use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from us may be monitored. Tue, 15 Jan 2013 16:12:38 GMT http://community.qnx.com/sf/go/post98577 Graham Watson 2013-01-15T16:12:38Z http://community.qnx.com/sf/go/post98567 The inode is a filesystem data structure that represents a file (its location on disk, owner, permissions, etc). If 2 "files" on the same partition have the same inode, they are actually 2 names for the same file. You can create many names for the same file with the command "ln". When you do "ls -l", the first value after the permissions is the number of files pointing to that inode, or should I say, the number of filenames corresponding to that file. Below, I have created file "myfile" and the link number is 1. After creating a second name for that same file with command "ln", we see that the number of links is 2 for each of those: # echo "Hello" > myfile # ls -l total 1 -rw-rw-r-- 1 root nto 6 Jan 15 09:07 myfile # ln myfile AnotherLinkToMyFyle # ls -l total 2 -rw-rw-r-- 2 root nto 6 Jan 15 09:07 AnotherLinkToMyFyle -rw-rw-r-- 2 root nto 6 Jan 15 09:07 myfile # echo "Hello again" > otherFile # ls -l total 3 -rw-rw-r-- 2 root nto 6 Jan 15 09:07 AnotherLinkToMyFyle -rw-rw-r-- 2 root nto 6 Jan 15 09:07 myfile -rw-rw-r-- 1 root nto 12 Jan 15 09:12 otherFile # See the inode number like the page number in a book. In addition to the inode, you have to check the partition. Inodes on different partitions are completely unrelated, like page numbers on 2 different books. Tue, 15 Jan 2013 14:22:17 GMT http://community.qnx.com/sf/go/post98567 Mario Beaulieu 2013-01-15T14:22:17Z http://community.qnx.com/sf/go/post98563 Hi, We have a system running on QNX 6.4.1 which makes use of filesystem resource managers. During an investigation it was discovered that several files in different directories have the same inode number. The inode number is assigned by the resource manager and is not left with a zero value to have one assigned by the O/S. Can anyone give me any information they might have that details the possible implications of having files in the same filesystem with non unique inode numbers. The files themselves are accessed in a variety of ways, From PHP, from O/S commands such as cat, more etc. and from O/S APIs open() and fopen(). The easy solution as you might point out is to make sure the inode numbers are non-unique, but we have systems in the field and urgently need to know if there are any known issues. Thanks for your help Tue, 15 Jan 2013 09:35:51 GMT http://community.qnx.com/sf/go/post98563 Graham Watson 2013-01-15T09:35:51Z http://community.qnx.com/sf/go/post98550 Thanks guys. I thought that file just only for restriction and ignored it. I will try it tomorrow and inform you. Regards. Mon, 14 Jan 2013 18:49:25 GMT http://community.qnx.com/sf/go/post98550 enes aykurt 2013-01-14T18:49:25Z http://community.qnx.com/sf/go/post98549 Good call on the /etc/ftpusers, I had forgotten about that file. Also, ignore the mount instructions that is for a device with a writable filesystem mounted as /base ;-) -----Original Message----- From: Mario Beaulieu [mailto:community-noreply@qnx.com] Sent: January-14-13 10:17 AM To: general-filesystems Subject: Re: RE: RE: ifs with ftp cabapility? To use FTP, you will need a file: /etc/ftpusers If this file is absent, all ftp accesses will be denied. In order to write in /etc (and in a few other directories), you need to remount the filesystem as writable. To do that: mount -uw /base ... now the system is writable ... do your stuff ... and restore it to read-only when you are done mount -ur /base Note that you cannot overwrite or modify a file. To do such a thing, you will need to rename or delete the original, then create the "modified" version. _______________________________________________ General http://community.qnx.com/sf/go/post98546 To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com Mon, 14 Jan 2013 16:45:51 GMT http://community.qnx.com/sf/go/post98549 Chris Travis 2013-01-14T16:45:51Z http://community.qnx.com/sf/go/post98546 To use FTP, you will need a file: /etc/ftpusers If this file is absent, all ftp accesses will be denied. In order to write in /etc (and in a few other directories), you need to remount the filesystem as writable. To do that: mount -uw /base ... now the system is writable ... do your stuff ... and restore it to read-only when you are done mount -ur /base Note that you cannot overwrite or modify a file. To do such a thing, you will need to rename or delete the original, then create the "modified" version. Mon, 14 Jan 2013 15:16:42 GMT http://community.qnx.com/sf/go/post98546 Mario Beaulieu 2013-01-14T15:16:42Z http://community.qnx.com/sf/go/post98538 A few options. Once you telnet into the target you can run ftp "from" the target to get the file to the target(in/dev/shmem), or if you really need to ftp into the target then you can put writable files into /dev/shmem ; just create a link in the build file from /etc/shadow to /dev/shmem/shadow. You could also use devf-ram to create a ram filesystem...that you could write to. Devb suggestion wasn't mine. Sent from my BlackBerry 10 smartphone. From: enes aykurt Sent: Sunday, January 13, 2013 4:57 PM To: general-filesystems Reply To: general-filesystems@community.qnx.com Subject: Re: RE: RE: ifs with ftp cabapility? Hi Chris, I have already done the telnet, my problem is about ftp. For ftp as you know I need also the shadow file because ftp user must have a password. However I could not figure out how to form and locate an encrypted file in ifs.I tried to form a shadow file by using a QNX disk system and used it on my ifs however that didnt work. Tomorrow I will try the devb driver modification that you have suggested. Can you please explain me the affect of this option ? regards _______________________________________________ General http://community.qnx.com/sf/go/post98536 To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com Sun, 13 Jan 2013 22:56:48 GMT http://community.qnx.com/sf/go/post98538 Chris Travis 2013-01-13T22:56:48Z http://community.qnx.com/sf/go/post98536 Hi Chris, I have already done the telnet, my problem is about ftp. For ftp as you know I need also the shadow file because ftp user must have a password. However I could not figure out how to form and locate an encrypted file in ifs.I tried to form a shadow file by using a QNX disk system and used it on my ifs however that didnt work. Tomorrow I will try the devb driver modification that you have suggested. Can you please explain me the affect of this option ? regards Sun, 13 Jan 2013 21:59:57 GMT http://community.qnx.com/sf/go/post98536 enes aykurt 2013-01-13T21:59:57Z http://community.qnx.com/sf/go/post98535 That will not help as you are not using a devb driver. You need to include all of the files necessary in the ifs including /etc/passwd Here is a link from the Support Knowledge Base that shows a build image with the necessary files that allows you to telnet into it: http://www.qnx.com/support/knowledgebase.html?id=50130000000SzKu Chris -----Original Message----- From: enes aykurt [mailto:community-noreply@qnx.com] Sent: January-13-13 9:40 AM To: general-filesystems Subject: Re: RE: ifs with ftp cabapility? can you please send me the documentation about that ? _______________________________________________ General http://community.qnx.com/sf/go/post98534 To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com Sun, 13 Jan 2013 15:25:08 GMT http://community.qnx.com/sf/go/post98535 Chris Travis 2013-01-13T15:25:08Z http://community.qnx.com/sf/go/post98534 can you please send me the documentation about that ? Sun, 13 Jan 2013 14:39:30 GMT http://community.qnx.com/sf/go/post98534 enes aykurt 2013-01-13T14:39:30Z http://community.qnx.com/sf/go/post98531 Try passing -osync=optional to devb-* -----Message d'origine----- De : enes aykurt [mailto:community-noreply@qnx.com] Envoyé : Saturday, January 12, 2013 10:58 PM À : general-filesystems Objet : ifs with ftp cabapility? Hi all, I have got an intel atom processor card and I am booting it by using an SSD. I created an ifs image and booted the card with it. However after boot I could not write/modify the etc, usr, bin, lib files on target. I think that is because of the image's read only property. But I need some services which will use those files dynamically. For example I need ftp service and as far as I know to use ftp a user should have a password. However to change the password, passwd utility using/modfiying the files under /etc. How can I manage to make those files writable? Where am I doing wrong? If someone help me I ll appretiate. Thanks and regards _______________________________________________ General http://community.qnx.com/sf/go/post98528 To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com Sat, 12 Jan 2013 18:03:42 GMT http://community.qnx.com/sf/go/post98531 Mario Charest 2013-01-12T18:03:42Z http://community.qnx.com/sf/go/post98528 Hi all, I have got an intel atom processor card and I am booting it by using an SSD. I created an ifs image and booted the card with it. However after boot I could not write/modify the etc, usr, bin, lib files on target. I think that is because of the image's read only property. But I need some services which will use those files dynamically. For example I need ftp service and as far as I know to use ftp a user should have a password. However to change the password, passwd utility using/modfiying the files under /etc. How can I manage to make those files writable? Where am I doing wrong? If someone help me I ll appretiate. Thanks and regards Sat, 12 Jan 2013 09:57:35 GMT http://community.qnx.com/sf/go/post98528 enes aykurt 2013-01-12T09:57:35Z http://community.qnx.com/sf/go/post98368 You seem to be using a OS Image Filesystem (IFS) build file with the mketfs utility which creates an Embedded Transaction FileSystem (ETFS). They are not the same things and the difference and usage is documented, please have a look: http://www.qnx.com/developers/docs/6.5.0_sp1/topic/com.qnx.doc.neutrino_building/building_nto.html?cp=13_2_3 http://www.qnx.com/developers/docs/6.5.0_sp1/topic/com.qnx.doc.neutrino_utilities/m/mkifs.html?cp=13_13_15_18 http://www.qnx.com/developers/docs/6.5.0_sp1/topic/com.qnx.doc.neutrino_utilities/m/mketfs.html?cp=13_13_15_15 [virtual] and [+script] are not supported in an mketfs build file. Fri, 04 Jan 2013 05:41:50 GMT http://community.qnx.com/sf/go/post98368 Eric Fausett 2013-01-04T05:41:50Z http://community.qnx.com/sf/go/post98331 Hi, I'm trying to run mketfs to create the filesystem with the following buildfile: [virtual=x86,bios +compress] .bootstrap = { startup-bios PATH=/proc/boot:/bin procnto } [+script] .script = { devc-con -e -n5 & reopen /dev/con1 devf-i365sl -r -b3 -m2 -u2 -t4 & waitfor /fs0p0 [+session] TERM=qansi PATH=/proc/boot:/bin esh & } [type=link] /tmp=/dev/shmem [type=link] /bin=/fs0p0/bin [type=link] /etc=/fs0p0/etc libc.so [type=link] /usr/lib/ldqnx.so.2=/proc/boot/libc.so libsocket.so [data=copy] devf-i365sl devc-con esh ---------------------------------------------- When I run the mketfs command I get an error with the [virtual] attribute. Is there a replace for this attribute? Is it needed with mketfs? Thanks in advance. I'm running QNX 6.4.1 Fri, 28 Dec 2012 19:57:34 GMT http://community.qnx.com/sf/go/post98331 Pablo Cepedal 2012-12-28T19:57:34Z http://community.qnx.com/sf/go/post98111 > Hello, > > I am writing a FFS3 NOR flash driver for an i.MX31 based board. The device is > a Spansion S71WS128PC0HF3 burst-mode NOR Flash (16MB, 16 bit bus width) > connected to CS5 of the WEIM. I can boot the system from this flash and I > created an EFS and burnt it into the flash via JTAG debugger. I wrote a small > test program that simply maps in the base address and scans for the 'QSSL' > signature of the partition - it finds it at the correct address. However, when > I run my flash driver it doesn't recognise it. > > The auto-detect of the device works ((devf t1::f3s_flash_probe:248) chip > total = 1, bus_width = 2, interleave = 1) > Erasing via flashctl works. > flashctl -p/dev/fs0 -o8M -l8M -e -v > Erasing device /dev/fs0 > ................................................................ > (devf t2::f3s_table_find:66) fs0p0 raw U: 80 > # > Formatting fails, though: > # flashctl -p/dev/fs0p0 -o8M -l8M -f -v > Formatting device /dev/fs0p0 > amd_poll: 163 program error > (devf t2::amd_v2wordwrite:113) over poll waiting for write completion > (devf t2::f3s_ext_write:197) fs0p0 bad H[00] P[40] # 000010 > DCMD_F3S_FORMAT failed (errno 5) > flashctl: format failed > > I tried various write() functions of the MTD library but always the same. > Maybe the writing works but reading doesn't? I supply NULL for the v2read > callout, so it should use memcpy(), which works, as seen from my test program. > > > Any ideas greatly appriciated. Thank you. > > -Albrecht hello , Gunter Geigemueller I met the same problem just the same as you.I can erase my flash use flashctl but can't format it, how did you fix it? Thank you very much. Formatting device /dev/fs0p0 amd_poll: 163 program error (devf t2::amd_v2wordwrite:113) over poll waiting for write completion (devf t2::f3s_ext_write:197) fs0p0 bad H[00] P[40] # 000010 DCMD_F3S_FORMAT failed (errno 5) flashctl: format failed Fri, 14 Dec 2012 08:28:46 GMT http://community.qnx.com/sf/go/post98111 Daniel Lee 2012-12-14T08:28:46Z http://community.qnx.com/sf/go/post97709 This isn't strictly a filesystem question, but this seems like the best place to ask: We have the following configuration: Secondary Master: Compact Flash (boot device, shows up as /dev/hd0) Primary Master: Fixed Hard Drive (shows up as /dev/hd1) Primary Slave: Removable Hard Drive (shows up as /dev/hd2) All drives are supported by devb-eide. The question is how to best manage the device removal and replacement. Under QNX4 we would umount /dev/hd2, then remove the drive. On replacement, we would mount -e /dev/hd2, then mount the partitions (no automount). Does devb-eide support a removable drive? I know that /dev/hd2 did not appear after the drive was inserted the first time. It showed up after a reboot. Worst case would be to shutdown the system whenever the drive needs to be inserted or removed. Other options might be shutting down the driver and restarting it as necessary, but I'm guessing I would have to first make sure I have separate driver invocations for primary and secondary, then umount both /dev/hd1 and /dev/hd2 before stopping the driver. Is there any facility for asking devb-eide to rescan the interfaces? Any other suggestions? Sat, 01 Dec 2012 17:59:31 GMT http://community.qnx.com/sf/go/post97709 Norton Allen 2012-12-01T17:59:31Z http://community.qnx.com/sf/go/post97484 I am getting this error during compilation of my code in a XP Pc. I have only NX installed for gcc. process_begin: CreateProcess(C:\Projects.Local\Embedded\SB\Core\Main\Tools\DiagUtil.com, ../../../Core/Main/Tools/DiagUtil.com /DiagCodesFile:DiagDef.h /Module:PPDA /UseClass:Pack /ImpXls:../../../Core/Main/Config_Files/CommonDiagnostics.xls /ImpXls:C:/Projects.Local/Embedded/SB/IOPack/Main/PPDA/Config_Files/PPDA_Diagnostics.xls /ExpDiagCodes:C:/Projects.Local/Embedded/SB/IOPack/Main/PPDA /ExpDiagMsgs:C:/Projects.Local/Embedded/SB/IOPack/Main/PPDA, ...) failed. make (e=5): Access is denied. make[1]: *** [diagsrc] Error 5 Please suggest. Tue, 27 Nov 2012 13:25:21 GMT http://community.qnx.com/sf/go/post97484 manas sahoo 2012-11-27T13:25:21Z http://community.qnx.com/sf/go/post96803 > When I read the bsp code , I saw cam_configure() in the devb directory. This > function is defined in libcam.so. Where I can get its doc or description? I > just could not find any infomation in the user guide. > > BR > Jerry Has anyone ver replied to this post. I could use the same info. RJG Fri, 02 Nov 2012 15:48:43 GMT http://community.qnx.com/sf/go/post96803 Richard Gawrelski 2012-11-02T15:48:43Z http://community.qnx.com/sf/go/post96537 From my own experience I would recommend checking number of free inodes on the disk, as it can be limiting the number of possible files on the disk. If necessary, create the filesystem with appropriate number of inodes. You can see these number with "chkqnx6fs -s" command Regards, PKY > The qnx6fs does not have any specific limit to the number of files or > directories that can be present on the disk. Of course disk space and > performance issues should be considered. File and directory look ups have an > O(N) cost. > > -----Original Message----- > From: Mark Bangert [mailto:community-noreply@qnx.com] > Sent: October-18-12 5:40 AM > To: general-filesystems > Subject: Re: Maximum limit for the number of directories and directory can > contain? > > QNX6 > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post96424 > To cancel your subscription to this discussion, please e-mail general- > filesystems-unsubscribe@community.qnx.com Tue, 23 Oct 2012 06:23:53 GMT http://community.qnx.com/sf/go/post96537 Pavol Kycina 2012-10-23T06:23:53Z http://community.qnx.com/sf/go/post96531 The qnx6fs does not have any specific limit to the number of files or directories that can be present on the disk. Of course disk space and performance issues should be considered. File and directory look ups have an O(N) cost. -----Original Message----- From: Mark Bangert [mailto:community-noreply@qnx.com] Sent: October-18-12 5:40 AM To: general-filesystems Subject: Re: Maximum limit for the number of directories and directory can contain? QNX6 _______________________________________________ General http://community.qnx.com/sf/go/post96424 To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com Mon, 22 Oct 2012 22:57:26 GMT http://community.qnx.com/sf/go/post96531 Keith Garvin 2012-10-22T22:57:26Z http://community.qnx.com/sf/go/post96424 QNX6 Thu, 18 Oct 2012 12:40:11 GMT http://community.qnx.com/sf/go/post96424 Mark Bangert 2012-10-18T12:40:11Z http://community.qnx.com/sf/go/post96422 What filesystem type? Thu, 18 Oct 2012 12:01:47 GMT http://community.qnx.com/sf/go/post96422 Dennis Kellly 2012-10-18T12:01:47Z http://community.qnx.com/sf/go/post96397 We recently got USB 3.0 device driver up and running on QNX for our board. I wanted to access a EMMC area available on the board and make it available as a storage area in the Host. In short I want my device to behave as a mass storage device. Is there and QNX SCSI related driver already available or do I have to write this driver from scratch. I recently saw a discussion on a libcam.so. Was wondering if I can use that for my operation. The EMMC area i have available is mounted and visible in \dev. Wed, 17 Oct 2012 16:44:15 GMT http://community.qnx.com/sf/go/post96397 Abhay Ravi Chandran 2012-10-17T16:44:15Z http://community.qnx.com/sf/go/post96394 Does anyone know if or what the maximum number of directories that can be created is. Our system creates a time stamped log file file in a new directory each time the system starts. Is there a limit on how many times this can be done?? Wed, 17 Oct 2012 15:23:00 GMT http://community.qnx.com/sf/go/post96394 Mark Bangert 2012-10-17T15:23:00Z http://community.qnx.com/sf/go/post95713 Yes, i want that. I think there are already exist something like that, but only for old qnx4-filesystems, not for qnx6-filesystems ? Like: http://qnxfs.narod.ru/ Thu, 20 Sep 2012 14:26:18 GMT http://community.qnx.com/sf/go/post95713 Esa Heikkinen 2012-09-20T14:26:18Z http://community.qnx.com/sf/go/post95711 You have a QNX6 FS on your disk, you booted Linux and you want Linux to see your files? A good question for a Linux forum. For almost sure, the answer is going to be "no." From: Esa Heikkinen <community-noreply@qnx.com<mailto:community-noreply@qnx.com>> Reply-To: <general-filesystems@community.qnx.com<mailto:general-filesystems@community.qnx.com>> Date: Thu, 20 Sep 2012 07:27:05 -0400 To: general-filesystems <general-filesystems@community.qnx.com<mailto:general-filesystems@community.qnx.com>> Subject: Mounting QNX6 new filesystems from other operating system Is it possible to mount new QNX6 filesystems (type 177, 178 and 179) from other operating systems like Linux ? _______________________________________________ General http://community.qnx.com/sf/go/post95697 To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com<mailto:general-filesystems-unsubscribe@community.qnx.com> Thu, 20 Sep 2012 13:59:53 GMT http://community.qnx.com/sf/go/post95711 Mate Szarvas 2012-09-20T13:59:53Z http://community.qnx.com/sf/go/post95697 Is it possible to mount new QNX6 filesystems (type 177, 178 and 179) from other operating systems like Linux ? Thu, 20 Sep 2012 11:27:05 GMT http://community.qnx.com/sf/go/post95697 Esa Heikkinen 2012-09-20T11:27:05Z http://community.qnx.com/sf/go/post95523 I think I have found what I am looking for: http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=/com.qnx.doc.neutrino_technotes/reloadable_ifs.html Wed, 12 Sep 2012 13:01:16 GMT http://community.qnx.com/sf/go/post95523 Devan Lippman 2012-09-12T13:01:16Z http://community.qnx.com/sf/go/post95508 Hello, I'm currently working with a system that uses a NAND resident ETFS filesystem. Since there are a large amount of executibles run here I was thinking that maybe performance could be increased by loading all the executibles/libraries in memory. I'm thinking this look something like a contiguous image stored in NAND (outside of ETFS) that gets copied to RAM, mounted and processes are spawned. Similar in nature to the boot image (or in linux initrd) but loaded after the kernel has begun. Does this line of thinking make sense to people more experienced with QNX? I was looking at devb-ram but this does not appear to be able to restore from an image. Is this something anyone has played with? Alternatively is there a way to have the ETFS system cached in RAM with write-back access? Although for this to show benefit I would imagine that the entire partition would need to be pre-cached? Thanks, Devan Tue, 11 Sep 2012 17:55:53 GMT http://community.qnx.com/sf/go/post95508 Devan Lippman 2012-09-11T17:55:53Z http://community.qnx.com/sf/go/post95147 The only reason I found this was as a result of a search for the string "Press F1-F4 to select drive or select partition 1,2,3? 1". This link kind of outlines everything. http://www.qnx.com/developers/docs/6.3.2/neutrino/user_guide/starting.html Again, thanks for the help. Mark Mon, 27 Aug 2012 14:21:12 GMT http://community.qnx.com/sf/go/post95147 Mark Bangert 2012-08-27T14:21:12Z http://community.qnx.com/sf/go/post95144 Excellent news! My pleasure... Can you send me a link to the documentation you found? Chris -----Original Message----- From: Mark Bangert [mailto:community-noreply@qnx.com] Sent: August-27-12 10:07 AM To: general-filesystems Subject: Re: RE: RE: RE: RE: Booting a Minimal QNX6.5 from a HardDrive Hi Chris, Success, thought you would like to know. The final piece of the puzzle was "dloader". I didn't realize that two loaders were required. It now makes sense. I found a piece of documentation over the weekend that solved the problem. Thank you ever so much for all of your help. Best Regards, Mark _______________________________________________ General http://community.qnx.com/sf/go/post95143 To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com Mon, 27 Aug 2012 14:08:44 GMT http://community.qnx.com/sf/go/post95144 Chris Travis 2012-08-27T14:08:44Z http://community.qnx.com/sf/go/post95143 Hi Chris, Success, thought you would like to know. The final piece of the puzzle was "dloader". I didn't realize that two loaders were required. It now makes sense. I found a piece of documentation over the weekend that solved the problem. Thank you ever so much for all of your help. Best Regards, Mark Mon, 27 Aug 2012 14:06:51 GMT http://community.qnx.com/sf/go/post95143 Mark Bangert 2012-08-27T14:06:51Z http://community.qnx.com/sf/go/post95131 Chris, I tried the mkqnxfs -B /dev/hd1T177 command and still no fire. If there is someone else that you think might be able to help that would be great. I really appreciate your help, you've been great. Have a good weekend. Mark Fri, 24 Aug 2012 20:21:04 GMT http://community.qnx.com/sf/go/post95131 Mark Bangert 2012-08-24T20:21:04Z http://community.qnx.com/sf/go/post95126 I'm not sure at this point, but I would think that the boot loader would have been written with the "mkqnx6fs /dev/hd1t177" command...but try rewriting the boot loader with: "mkqnx6fs -B /dev/hd1t177" If this doesn't work, then I'll get one of the file system guys to jump in. -----Original Message----- From: Mark Bangert [mailto:community-noreply@qnx.com] Sent: August-24-12 11:08 AM To: general-filesystems Cc: DWarnock@Medrobotics.com Subject: Re: RE: RE: RE: Booting a Minimal QNX6.5 from a HardDrive Chris, I'm so close. I re-did the "mkqnx6fs /dev/hd1t177" command just in case screwed up something. I then moved a copy of my bootable ifs image that's on hd0 to the /fs/hd1-qnx6/.boot directory. I know that this is a working image. I remove hd0 and make hd1 my new hd0 and boot. I get the qnx "v1.2b Boot loader:" message but that's it. What I have noticed is that there is a previous message that I get with the working hd0 "Press F1-F4 to select drive or select Partition:", I don't get this message with my hd. Also another bit of information. If I have both drives in the system and when it boots I can select drive 2 and it will boot from drive 2. So it seems to me that I'm still missing something in the preperation of my drive. Something is still missing. Regards, Mark _______________________________________________ General http://community.qnx.com/sf/go/post95117 To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com Fri, 24 Aug 2012 17:07:27 GMT http://community.qnx.com/sf/go/post95126 Chris Travis 2012-08-24T17:07:27Z http://community.qnx.com/sf/go/post95117 Chris, I'm so close. I re-did the "mkqnx6fs /dev/hd1t177" command just in case screwed up something. I then moved a copy of my bootable ifs image that's on hd0 to the /fs/hd1-qnx6/.boot directory. I know that this is a working image. I remove hd0 and make hd1 my new hd0 and boot. I get the qnx "v1.2b Boot loader:" message but that's it. What I have noticed is that there is a previous message that I get with the working hd0 "Press F1-F4 to select drive or select Partition:", I don't get this message with my hd. Also another bit of information. If I have both drives in the system and when it boots I can select drive 2 and it will boot from drive 2. So it seems to me that I'm still missing something in the preperation of my drive. Something is still missing. Regards, Mark Fri, 24 Aug 2012 15:08:11 GMT http://community.qnx.com/sf/go/post95117 Mark Bangert 2012-08-24T15:08:11Z http://community.qnx.com/sf/go/post95109 /fs/hd1-qnx6/.boot/ is a directory, which is where you need to put you're ifs. You may have written over your /fs/hd1-qnx6/.boot/ directory with your cp command ;-) If so, you would have to rerun the mkqnx6fs command to recreate the qnx6 filesystem. When you remove the hd0 drive then reboot; the loader(on the secondary disk which is now the primary) should show your ifs as a selection to boot from. Once booted, as long as you have the io-blk driver(and required libs) running in your ifs, then the hard-drive should show up as /dev/hd0 and hopefully be mounted as / Now this filesystem will be empty unless you've copied files over to the /fs/hd1-qnx6/ previous to removing the initial disk. If you get as far as selecting you're image and it doesn't boot properly, post your myqnx.build file. Chris -----Original Message----- From: Mark Bangert [mailto:community-noreply@qnx.com] Sent: August-23-12 5:36 PM To: general-filesystems Subject: Re: RE: RE: Booting a Minimal QNX6.5 from a HardDrive Almost there. After performing the above, and rebooting I get a meessage on the screen "QNX v1.2b Boot Loader" and a blinking cursor. I think the issue is not being able to copy my ifs from one drive to another. This is basic but I'm have trouble. I believe the command should be cp myqnx.ifs /fs/hd1-qnx6/.boot and the ifs goes from hd0 to hd1. regards, Mark _______________________________________________ General http://community.qnx.com/sf/go/post95103 To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com Fri, 24 Aug 2012 05:50:59 GMT http://community.qnx.com/sf/go/post95109 Chris Travis 2012-08-24T05:50:59Z http://community.qnx.com/sf/go/post95103 Almost there. After performing the above, and rebooting I get a meessage on the screen "QNX v1.2b Boot Loader" and a blinking cursor. I think the issue is not being able to copy my ifs from one drive to another. This is basic but I'm have trouble. I believe the command should be cp myqnx.ifs /fs/hd1-qnx6/.boot and the ifs goes from hd0 to hd1. regards, Mark Thu, 23 Aug 2012 21:35:37 GMT http://community.qnx.com/sf/go/post95103 Mark Bangert 2012-08-23T21:35:37Z http://community.qnx.com/sf/go/post95093 So this is good, you have a bootable partition on your disk...ignore the fdisk /dev/hd1t77 wrt. fdisk. So now you need to run "mkqnx6fs /dev/hd1t77" to create the qnx6 filesystem on your partition. Then reboot/restart the io-blk driver, and put your disk partition should show up as /fs/hd1-qnx6 and put your ifs file in /fs/hd1-qnx6/.boot/ Then power off and remove your /dev/hd0 disk, upon reboot the loader should show you the ifs that is in your /.boot/ -----Original Message----- From: Mark Bangert [mailto:community-noreply@qnx.com] Sent: August-23-12 2:42 PM To: general-filesystems Subject: Re: RE: Booting a Minimal QNX6.5 from a HardDrive If you do an fdisk /dev/hd1 show you get: _____OS_____ Start End ______Number_____ Size Boot name type Cylinder Cylinder Cylinders Blocks 1. QNX6 (177) 0 19456 19457 312576642 152625 MB * 2. ______ (___) _______ _______ _______ _________ _____ 3. ______ (___) _______ _______ _______ _________ _____ 4. ______ (___) _______ _______ _______ _________ _____ If you do fdisk /dev/hd1t177 show you get: _____OS_____ Start End ______Number_____ Size Boot name type Cylinder Cylinder Cylinders Blocks 1. nonQNX (114) 242288 255782 13495 216793029 105855 MB * 2. __dos_ (_6_) 204664 205699 1036 16641012 8125 MB * 3. ______ (___) _______ _______ _______ _________ _____ 4. ______ (___) _______ _______ _______ _________ _____ _______________________________________________ General http://community.qnx.com/sf/go/post95089 To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com Thu, 23 Aug 2012 19:15:33 GMT http://community.qnx.com/sf/go/post95093 Chris Travis 2012-08-23T19:15:33Z http://community.qnx.com/sf/go/post95089 If you do an fdisk /dev/hd1 show you get: _____OS_____ Start End ______Number_____ Size Boot name type Cylinder Cylinder Cylinders Blocks 1. QNX6 (177) 0 19456 19457 312576642 152625 MB * 2. ______ (___) _______ _______ _______ _________ _____ 3. ______ (___) _______ _______ _______ _________ _____ 4. ______ (___) _______ _______ _______ _________ _____ If you do fdisk /dev/hd1t177 show you get: _____OS_____ Start End ______Number_____ Size Boot name type Cylinder Cylinder Cylinders Blocks 1. nonQNX (114) 242288 255782 13495 216793029 105855 MB * 2. __dos_ (_6_) 204664 205699 1036 16641012 8125 MB * 3. ______ (___) _______ _______ _______ _________ _____ 4. ______ (___) _______ _______ _______ _________ _____ Thu, 23 Aug 2012 18:41:39 GMT http://community.qnx.com/sf/go/post95089 Mark Bangert 2012-08-23T18:41:39Z http://community.qnx.com/sf/go/post95087 "show" just prints the disk partition table...without it you can manipulate it. /dev/hd1 is the raw partition, whereas /dev/hd1t77 is the QNX6 partition(don't do anything with this one) What does the output of "fdisk /dev/hd1 show" say? -----Original Message----- From: Mark Bangert [mailto:community-noreply@qnx.com] Sent: August-23-12 1:13 PM To: general-filesystems Subject: Re: Booting a Minimal QNX6.5 from a HardDrive what is the difference between these two commands; fdisk /dev/hd1 show and fdisk /dev/hd1t177 I get two very different results, which one is correct? _______________________________________________ General http://community.qnx.com/sf/go/post95083 To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com Thu, 23 Aug 2012 18:26:34 GMT http://community.qnx.com/sf/go/post95087 Chris Travis 2012-08-23T18:26:34Z http://community.qnx.com/sf/go/post95083 what is the difference between these two commands; fdisk /dev/hd1 show and fdisk /dev/hd1t177 I get two very different results, which one is correct? Thu, 23 Aug 2012 17:12:45 GMT http://community.qnx.com/sf/go/post95083 Mark Bangert 2012-08-23T17:12:45Z http://community.qnx.com/sf/go/post95069 It appears you did... dinit -h /dev/hd0 or mkqnx6fs /dev/hd0 These would destroy the partition table as your post indicates. Use fdisk first and create the type of partition you want ... 77 or 177 (qnx6fs) Then specify the partition device, i.e. /dev/hd0t177 rather than /dev/hd0. Thu, 23 Aug 2012 13:12:17 GMT http://community.qnx.com/sf/go/post95069 Dennis Kellly 2012-08-23T13:12:17Z http://community.qnx.com/sf/go/post95068 Thank for the response. No there is no message of any kind. My first problem is I think that I'm not get the disk formatted correctly because the partition table look very strange. _____OS_____ Start End ______Number_____ Size Boot name type Cylinder Cylinder Cylinders Blocks 1. nonQNX 205 87476 87507 32 506704 247 MB * 2. nonQNX 88 0 4294967295 0 0 0 MB * 3. ______ (___) _______ _______ _______ _________ _____ 4. ______ (___) _______ _______ _______ _________ _____ Thu, 23 Aug 2012 12:58:26 GMT http://community.qnx.com/sf/go/post95068 Mark Bangert 2012-08-23T12:58:26Z http://community.qnx.com/sf/go/post95067 Is there an error message when it fails to boot? Thu, 23 Aug 2012 12:51:28 GMT http://community.qnx.com/sf/go/post95067 Dennis Kellly 2012-08-23T12:51:28Z http://community.qnx.com/sf/go/post95059 These resources should help you: http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=/com.qnx.doc.neutrino_technotes/qnx6bootloader.html http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=/com.qnx.doc.neutrino_utilities/d/dinit.html http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=/com.qnx.doc.neutrino_utilities/f/fs-qnx6.so.html -----Original Message----- From: Mark Bangert [mailto:community-noreply@qnx.com] Sent: August-22-12 5:43 PM To: general-filesystems Subject: Booting a Minimal QNX6.5 from a HardDrive The project that I'm working on requires a minimal QNX 6.5 system witch runs on an x86 platform. Currently the .ifs image we are using can be booted from a Thumb drive and works great. I now have to move this image to a Hard Drive. I can fdisk and mount the drive and I can copy files to it, but when I make the hard drive the main boot device it won"t boot. I not sure what boot loader I'm suppose to be using and I'm also not sure if the drive is formated correctly. I'm sure someone has done this before, and I'm looking for some direction. Regards, Mark _______________________________________________ General http://community.qnx.com/sf/go/post95049 To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com Thu, 23 Aug 2012 02:45:32 GMT http://community.qnx.com/sf/go/post95059 Chris Travis 2012-08-23T02:45:32Z http://community.qnx.com/sf/go/post95049 The project that I'm working on requires a minimal QNX 6.5 system witch runs on an x86 platform. Currently the .ifs image we are using can be booted from a Thumb drive and works great. I now have to move this image to a Hard Drive. I can fdisk and mount the drive and I can copy files to it, but when I make the hard drive the main boot device it won"t boot. I not sure what boot loader I'm suppose to be using and I'm also not sure if the drive is formated correctly. I'm sure someone has done this before, and I'm looking for some direction. Regards, Mark Wed, 22 Aug 2012 21:42:49 GMT http://community.qnx.com/sf/go/post95049 Mark Bangert 2012-08-22T21:42:49Z http://community.qnx.com/sf/go/post94721 Just look at an existing implementation. For example, I used the Atmel AT91SAM BSP. Then, I used the existing Linux code for my board to see how to implement the low-level code and glued all together. Wasn't fun, but got there eventually. > Hello todd, > I'm also porting SD card filesystem on QNX. I write low level driver > for SDHC card and test read() write() etc. ok, and I want to kown how to hook > on the sim system? Is there some document about that? Thank you. Thu, 09 Aug 2012 16:06:18 GMT http://community.qnx.com/sf/go/post94721 Todd Peterson 2012-08-09T16:06:18Z http://community.qnx.com/sf/go/post94706 Hello todd, I'm also porting SD card filesystem on QNX. I write low level driver for SDHC card and test read() write() etc. ok, and I want to kown how to hook on the sim system? Is there some document about that? Thank you. Thu, 09 Aug 2012 06:46:00 GMT http://community.qnx.com/sf/go/post94706 Daniel Lee 2012-08-09T06:46:00Z http://community.qnx.com/sf/go/post94544 Is it possible to get a dloader source code ? Tue, 31 Jul 2012 21:59:16 GMT http://community.qnx.com/sf/go/post94544 janusz ruszel 2012-07-31T21:59:16Z http://community.qnx.com/sf/go/post94542 Then you will need a dloader program that has been re-compiled to run under 6.2.0. Those errors are because the libc.so.3 will not be used until after you build it into a new IFS, which will require putting a 6.5.0 bootimage onto the device. The LD_PRELOAD environment variable is an attempt to make the load still try the new libc.so.3, even though the 6.2.0 libc.so.3 is already loaded from /proc/boot. > -----Original Message----- > From: janusz ruszel [mailto:community-noreply@qnx.com] > Sent: July-31-12 5:43 PM > To: general-filesystems > Subject: Re: RE: Upgrade QNX 6.2 bootable CF to bootable QNX 6.5 without > formatting > > I did copy QNX 6.5 c library together with dloader from QNX 6.5. Yes, it works > under QNX 6.5. The point is to upgrade the loader to 6.5 version when the 6.2 > is still running. > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post94541 > To cancel your subscription to this discussion, please e-mail general- > filesystems-unsubscribe@community.qnx.com Tue, 31 Jul 2012 21:45:47 GMT http://community.qnx.com/sf/go/post94542 David Sarrazin 2012-07-31T21:45:47Z http://community.qnx.com/sf/go/post94540 I guess that board supports Intel Advanced Programmable Interrupt Controllers (APIC). Did you start startup-apic program ? If so, we have had similar issue with another brand name board as well. Tue, 31 Jul 2012 21:43:56 GMT http://community.qnx.com/sf/go/post94540 janusz ruszel 2012-07-31T21:43:56Z http://community.qnx.com/sf/go/post94541 I did copy QNX 6.5 c library together with dloader from QNX 6.5. Yes, it works under QNX 6.5. The point is to upgrade the loader to 6.5 version when the 6.2 is still running. Tue, 31 Jul 2012 21:42:47 GMT http://community.qnx.com/sf/go/post94541 janusz ruszel 2012-07-31T21:42:47Z http://community.qnx.com/sf/go/post94539 Janusz, Those symbols require the new 6.5.0 libc.so.3, so you will need to make a new QNX boot image with 6.5.0 libraries before you can run the utility. You might have success if you set LD_PRELOAD=<path of 6.5 libc.so.3>. David > -----Original Message----- > From: janusz ruszel [mailto:community-noreply@qnx.com] > Sent: July-31-12 5:36 PM > To: general-filesystems > Subject: Upgrade QNX 6.2 bootable CF to bootable QNX 6.5 without > formatting > > How to update boot loader on the CF card formatted and bootable under > QNX 6.2 to QNX 6.5. I need to update boot loader only since 6.2 bootloader > does not work with 6.5 .boot image. The flash card can not be re-formatted. I > was attempting to run 6.5 dloader under QNX 6.2 with added libc.so.3 library > and new pc2 file but I am getting not resolved symbols error : > > unknown symbol: __deregister_frame_info > unknown symbol: _Jv_RegisterClasses > unknown symbol: __register_frame_info > unknown symbol: __deregister_frame_info > unknown symbol: __register_frame_info > > Any helpful solution or suggestion are really appreciate. > Janusz > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post94538 > To cancel your subscription to this discussion, please e-mail general- > filesystems-unsubscribe@community.qnx.com Tue, 31 Jul 2012 21:40:00 GMT http://community.qnx.com/sf/go/post94539 David Sarrazin 2012-07-31T21:40:00Z http://community.qnx.com/sf/go/post94538 How to update boot loader on the CF card formatted and bootable under QNX 6.2 to QNX 6.5. I need to update boot loader only since 6.2 bootloader does not work with 6.5 .boot image. The flash card can not be re-formatted. I was attempting to run 6.5 dloader under QNX 6.2 with added libc.so.3 library and new pc2 file but I am getting not resolved symbols error : unknown symbol: __deregister_frame_info unknown symbol: _Jv_RegisterClasses unknown symbol: __register_frame_info unknown symbol: __deregister_frame_info unknown symbol: __register_frame_info Any helpful solution or suggestion are really appreciate. Janusz Tue, 31 Jul 2012 21:35:49 GMT http://community.qnx.com/sf/go/post94538 janusz ruszel 2012-07-31T21:35:49Z http://community.qnx.com/sf/go/post93660 I have to make a new QNX 6.2.1 bootable image with QNX4 fie system on a CF-card. Can I initialize the CF-card (including bootloader) using QNX 6.3.2? Using QNX 6.3.2 for this will simplyfy the process, using a USB - CF Card Reader preparing the CF-card. I guess that my question boils down to: Can I use the same bootloader for QNX 6.3.2 and QNX 6.2.1? Mikael Thu, 14 Jun 2012 12:46:59 GMT http://community.qnx.com/sf/go/post93660 Mikael Eriksen 2012-06-14T12:46:59Z http://community.qnx.com/sf/go/post93619 I have ported Micron MT29F4G08 driver from other BSPs to MPC8313 device. This seems to be working and I have "/dev/etfs1", "/dev/etfs2" "fs/etfs" etc and have wrote a small appllication which created a file on fs/etfs, wrote some data to this and read it back successfully. I have however noticed in target file system navigator that I cannot browse into folder fs and its size is showing as zero. It is possible to browse folder fs from the console and also possible to copy folder fs from target file system navigator to my desktop ending with the following structure: fs/etfs/.badblks fs/etfs/.counts fs/etfs/.filetable fs/etfs/.reserved fs/etfs/<files_I_created> Should I be able to access folder fs from target file system navigator, if so any idea what could be going wrong for me? Also any advice on the approach to use for validating my driver would be appreciated? Thanks. Tue, 12 Jun 2012 17:26:21 GMT http://community.qnx.com/sf/go/post93619 Alistair Boyd 2012-06-12T17:26:21Z http://community.qnx.com/sf/go/post93461 Hi Oleg, As I can see, you should use flashctl utility for the mounting purpose. For example: >> flashctl -p *.efs -n /mnt/flash -m Fri, 01 Jun 2012 16:49:12 GMT http://community.qnx.com/sf/go/post93461 Olga Pronina 2012-06-01T16:49:12Z http://community.qnx.com/sf/go/post93453 Thanks, David. I'll give this a try. Fri, 01 Jun 2012 13:59:47 GMT http://community.qnx.com/sf/go/post93453 Jacky Li 2012-06-01T13:59:47Z http://community.qnx.com/sf/go/post93438 pathmgr_symlink() is more like resmgr_attach() than symlink(). It requires that you have root privileges. Fri, 01 Jun 2012 01:41:15 GMT http://community.qnx.com/sf/go/post93438 David Sarrazin 2012-06-01T01:41:15Z http://community.qnx.com/sf/go/post93432 Hi there, I am trying to use pathmgr_symlink() to create a symlink, but I am getting errno=EPERM (operation not permitted), while symlink() works. Can anyone please help explain why I am getting EPERM? Regards, Thu, 31 May 2012 21:46:53 GMT http://community.qnx.com/sf/go/post93432 Jacky Li 2012-05-31T21:46:53Z http://community.qnx.com/sf/go/post93420 Ok, I finally found it out. I rebooted the whole system and was able to mount everything. May be there was a lock put on a file somewhere. Thanks, David. Le 31.05.2012 17:03, David Billard a écrit : > Ok, I found the "mount -t qnx6". Now I have a mounting problem. I can mount the > partitions: > /dev/hd0t77.1 > /dev/hd0t77.2 > /dev/hd0t77.3 > /dev/hd0t77.4 > /dev/hd0t77.5 > > But not the /dev/hd0t77 (which is the biggest partition but the numbering scheme > suggests that this partition is subdivided in 1 to 5 sub partitions). Does it > means that there is an unpartitionned (and unformatted) space on the drive? > > Many thanks, > > David. > Le 31.05.2012 16:37, David Billard a écrit : >> Hi David, >> >> Sorry to bother you with my problem. How can I mount a qnx6 file system (I'm >> using the boot CD)? >> >> Many thanks, >> >> David. >> >> Le 15.05.2012 16:35, David Sarrazin a écrit : >>> What OS version are you running? Partition type 77 is normally reserved for partitions of type QNX4. Fdisk should say "QNX4" , simply because the type is 77. You can also try chkqnx6fs, on the off chance that the disks are formatted with the QNX6 file system. >>> >>> David >>> >>>> -----Original Message----- >>>> From: David Billard [mailto:community-noreply@qnx.com] >>>> Sent: May-15-12 10:33 AM >>>> To: general-filesystems@community.qnx.com >>>> Subject: Re: Mounting qnx4 fs with errors >>>> >>>> Hi David, >>>> >>>> it says that my partition is not a QNX4 fs. A rapid view with fdisk says >>>> "unknown loader". Is there any way to detect which fs is on the partitions >>>> (I'm almost sure it's qnx4, but perhaps am i wrong). >>>> >>>> many thanks, >>>> >>>> David. >>>> >>>> Le 15.05.2012 16:21, David Sarrazin a écrit : >>>>> First thing to try is chkfsys, which is the QNX4 file system checker tool. If >>>> you don't want to make any changes to the disk, the -f option will prevent >>>> the tool from modifying anything. >>>>> >>>>>> -----Original Message----- >>>>>> From: David Billard [mailto:community-noreply@qnx.com] >>>>>> Sent: May-15-12 10:35 AM >>>>>> To: general-filesystems >>>>>> Subject: Mounting qnx4 fs with errors >>>>>> >>>>>> Dear all, >>>>>> >>>>>> I'm new to QNX. I would like to recover files from a qnx4 filesystem >>>>>> on a harddrive. The hardrive has 6 partitions. I used the BOOT-CD and >>>>>> the photon file manager. If I do a df, it sees : >>>>>> >>>>>> /dev/hd0 >>>>>> /dev/hd0t77 >>>>>> /dev/hd0t77.1 >>>>>> /dev/hd0t77.2 >>>>>> /dev/hd0t77.3 >>>>>> /dev/hd0t77.4 >>>>>> /dev/hd0t77.5 >>>>>> >>>>>> If I try to mount /dev/hd0t77 or any of its declination, it says that >>>>>> the fs is corrupted. >>>>>> >>>>>> To my knowledge, the disk is not damaged. Do you see any reason for >>>>>> this message or any solution for me? >>>>>> >>>>>> Is there a way to fix the fs? >>>>>> >>>>>> Many thanks, >>>>>> >>>>>> david. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> >>>>>> General >>>>>> http://community.qnx.com/sf/go/post93087 >>>>>> To cancel your subscription to this discussion, please e-mail >>>>>> general- filesystems-unsubscribe@community.qnx.com >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> >>>>> General >>>>> http://community.qnx.com/sf/go/post93088 >>>>> To cancel your subscription to this discussion, please e-mail >>>>> general-filesystems-unsubscribe@community.qnx.com >>>> >>>> -- >>>> Prof. David Billard | David.Billard@hesge.ch >>>> University of Applied Sciences in Geneva | tel: +41 22 388 1885 >>>> Bât. F, 7 route de Drize - CH-1227 Carouge | fax: +41 22 388 1701 >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> >>>> General >>>> http://community.qnx.com/sf/go/post93090 >>>> To cancel your subscription to this discussion, please e-mail general- >>>> filesystems-unsubscribe@community.qnx.com >>> >>> >>> >>> >>> _______________________________________________ >>> >>> General >>> http://community.qnx.com/sf/go/post93091 >>> To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com >> > -- Prof. David Billard | David.Billard@hesge.ch University of Applied Sciences in Geneva | tel: +41 22 388 1885 Bât. F, 7 route de Drize - CH-1227 Carouge | fax: +41 22 388 1701 Thu, 31 May 2012 15:37:31 GMT http://community.qnx.com/sf/go/post93420 David Billard 2012-05-31T15:37:31Z http://community.qnx.com/sf/go/post93414 Ok, I found the "mount -t qnx6". Now I have a mounting problem. I can mount the partitions: /dev/hd0t77.1 /dev/hd0t77.2 /dev/hd0t77.3 /dev/hd0t77.4 /dev/hd0t77.5 But not the /dev/hd0t77 (which is the biggest partition but the numbering scheme suggests that this partition is subdivided in 1 to 5 sub partitions). Does it means that there is an unpartitionned (and unformatted) space on the drive? Many thanks, David. Le 31.05.2012 16:37, David Billard a écrit : > Hi David, > > Sorry to bother you with my problem. How can I mount a qnx6 file system (I'm > using the boot CD)? > > Many thanks, > > David. > > Le 15.05.2012 16:35, David Sarrazin a écrit : >> What OS version are you running? Partition type 77 is normally reserved for partitions of type QNX4. Fdisk should say "QNX4" , simply because the type is 77. You can also try chkqnx6fs, on the off chance that the disks are formatted with the QNX6 file system. >> >> David >> >>> -----Original Message----- >>> From: David Billard [mailto:community-noreply@qnx.com] >>> Sent: May-15-12 10:33 AM >>> To: general-filesystems@community.qnx.com >>> Subject: Re: Mounting qnx4 fs with errors >>> >>> Hi David, >>> >>> it says that my partition is not a QNX4 fs. A rapid view with fdisk says >>> "unknown loader". Is there any way to detect which fs is on the partitions >>> (I'm almost sure it's qnx4, but perhaps am i wrong). >>> >>> many thanks, >>> >>> David. >>> >>> Le 15.05.2012 16:21, David Sarrazin a écrit : >>>> First thing to try is chkfsys, which is the QNX4 file system checker tool. If >>> you don't want to make any changes to the disk, the -f option will prevent >>> the tool from modifying anything. >>>> >>>>> -----Original Message----- >>>>> From: David Billard [mailto:community-noreply@qnx.com] >>>>> Sent: May-15-12 10:35 AM >>>>> To: general-filesystems >>>>> Subject: Mounting qnx4 fs with errors >>>>> >>>>> Dear all, >>>>> >>>>> I'm new to QNX. I would like to recover files from a qnx4 filesystem >>>>> on a harddrive. The hardrive has 6 partitions. I used the BOOT-CD and >>>>> the photon file manager. If I do a df, it sees : >>>>> >>>>> /dev/hd0 >>>>> /dev/hd0t77 >>>>> /dev/hd0t77.1 >>>>> /dev/hd0t77.2 >>>>> /dev/hd0t77.3 >>>>> /dev/hd0t77.4 >>>>> /dev/hd0t77.5 >>>>> >>>>> If I try to mount /dev/hd0t77 or any of its declination, it says that >>>>> the fs is corrupted. >>>>> >>>>> To my knowledge, the disk is not damaged. Do you see any reason for >>>>> this message or any solution for me? >>>>> >>>>> Is there a way to fix the fs? >>>>> >>>>> Many thanks, >>>>> >>>>> david. >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> >>>>> General >>>>> http://community.qnx.com/sf/go/post93087 >>>>> To cancel your subscription to this discussion, please e-mail >>>>> general- filesystems-unsubscribe@community.qnx.com >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> >>>> General >>>> http://community.qnx.com/sf/go/post93088 >>>> To cancel your subscription to this discussion, please e-mail >>>> general-filesystems-unsubscribe@community.qnx.com >>> >>> -- >>> Prof. David Billard | David.Billard@hesge.ch >>> University of Applied Sciences in Geneva | tel: +41 22 388 1885 >>> Bât. F, 7 route de Drize - CH-1227 Carouge | fax: +41 22 388 1701 >>> >>> >>> >>> >>> >>> _______________________________________________ >>> >>> General >>> http://community.qnx.com/sf/go/post93090 >>> To cancel your subscription to this discussion, please e-mail general- >>> filesystems-unsubscribe@community.qnx.com >> >> >> >> >> _______________________________________________ >> >> General >> http://community.qnx.com/sf/go/post93091 >> To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com > -- Prof. David Billard | David.Billard@hesge.ch University of Applied Sciences in Geneva | tel: +41 22 388 1885 Bât. F, 7 route de Drize - CH-1227 Carouge | fax: +41 22 388 1701 Thu, 31 May 2012 15:06:41 GMT http://community.qnx.com/sf/go/post93414 David Billard 2012-05-31T15:06:41Z http://community.qnx.com/sf/go/post93407 Hi David, Sorry to bother you with my problem. How can I mount a qnx6 file system (I'm using the boot CD)? Many thanks, David. Le 15.05.2012 16:35, David Sarrazin a écrit : > What OS version are you running? Partition type 77 is normally reserved for partitions of type QNX4. Fdisk should say "QNX4" , simply because the type is 77. You can also try chkqnx6fs, on the off chance that the disks are formatted with the QNX6 file system. > > David > >> -----Original Message----- >> From: David Billard [mailto:community-noreply@qnx.com] >> Sent: May-15-12 10:33 AM >> To: general-filesystems@community.qnx.com >> Subject: Re: Mounting qnx4 fs with errors >> >> Hi David, >> >> it says that my partition is not a QNX4 fs. A rapid view with fdisk says >> "unknown loader". Is there any way to detect which fs is on the partitions >> (I'm almost sure it's qnx4, but perhaps am i wrong). >> >> many thanks, >> >> David. >> >> Le 15.05.2012 16:21, David Sarrazin a écrit : >>> First thing to try is chkfsys, which is the QNX4 file system checker tool. If >> you don't want to make any changes to the disk, the -f option will prevent >> the tool from modifying anything. >>> >>>> -----Original Message----- >>>> From: David Billard [mailto:community-noreply@qnx.com] >>>> Sent: May-15-12 10:35 AM >>>> To: general-filesystems >>>> Subject: Mounting qnx4 fs with errors >>>> >>>> Dear all, >>>> >>>> I'm new to QNX. I would like to recover files from a qnx4 filesystem >>>> on a harddrive. The hardrive has 6 partitions. I used the BOOT-CD and >>>> the photon file manager. If I do a df, it sees : >>>> >>>> /dev/hd0 >>>> /dev/hd0t77 >>>> /dev/hd0t77.1 >>>> /dev/hd0t77.2 >>>> /dev/hd0t77.3 >>>> /dev/hd0t77.4 >>>> /dev/hd0t77.5 >>>> >>>> If I try to mount /dev/hd0t77 or any of its declination, it says that >>>> the fs is corrupted. >>>> >>>> To my knowledge, the disk is not damaged. Do you see any reason for >>>> this message or any solution for me? >>>> >>>> Is there a way to fix the fs? >>>> >>>> Many thanks, >>>> >>>> david. >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> >>>> General >>>> http://community.qnx.com/sf/go/post93087 >>>> To cancel your subscription to this discussion, please e-mail >>>> general- filesystems-unsubscribe@community.qnx.com >>> >>> >>> >>> >>> _______________________________________________ >>> >>> General >>> http://community.qnx.com/sf/go/post93088 >>> To cancel your subscription to this discussion, please e-mail >>> general-filesystems-unsubscribe@community.qnx.com >> >> -- >> Prof. David Billard | David.Billard@hesge.ch >> University of Applied Sciences in Geneva | tel: +41 22 388 1885 >> Bât. F, 7 route de Drize - CH-1227 Carouge | fax: +41 22 388 1701 >> >> >> >> >> >> _______________________________________________ >> >> General >> http://community.qnx.com/sf/go/post93090 >> To cancel your subscription to this discussion, please e-mail general- >> filesystems-unsubscribe@community.qnx.com > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post93091 > To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com -- Prof. David Billard | David.Billard@hesge.ch University of Applied Sciences in Geneva | tel: +41 22 388 1885 Bât. F, 7 route de Drize - CH-1227 Carouge | fax: +41 22 388 1701 Thu, 31 May 2012 14:44:17 GMT http://community.qnx.com/sf/go/post93407 David Billard 2012-05-31T14:44:17Z http://community.qnx.com/sf/go/post93103 I'm using the boot-cd "qnxsdp-6.4.1-x86-200905201802-nto.iso". chkqnx6fs returns nothing. That is it does something but then the prompt appears and nothing is displayed at the screen. Does it means it is really qnx6? In that case, do I need a special driver for qnx6 fs? David. Le 15.05.2012 16:35, David Sarrazin a écrit : > What OS version are you running? Partition type 77 is normally reserved for partitions of type QNX4. Fdisk should say "QNX4" , simply because the type is 77. You can also try chkqnx6fs, on the off chance that the disks are formatted with the QNX6 file system. > > David > >> -----Original Message----- >> From: David Billard [mailto:community-noreply@qnx.com] >> Sent: May-15-12 10:33 AM >> To: general-filesystems@community.qnx.com >> Subject: Re: Mounting qnx4 fs with errors >> >> Hi David, >> >> it says that my partition is not a QNX4 fs. A rapid view with fdisk says >> "unknown loader". Is there any way to detect which fs is on the partitions >> (I'm almost sure it's qnx4, but perhaps am i wrong). >> >> many thanks, >> >> David. >> >> Le 15.05.2012 16:21, David Sarrazin a écrit : >>> First thing to try is chkfsys, which is the QNX4 file system checker tool. If >> you don't want to make any changes to the disk, the -f option will prevent >> the tool from modifying anything. >>> >>>> -----Original Message----- >>>> From: David Billard [mailto:community-noreply@qnx.com] >>>> Sent: May-15-12 10:35 AM >>>> To: general-filesystems >>>> Subject: Mounting qnx4 fs with errors >>>> >>>> Dear all, >>>> >>>> I'm new to QNX. I would like to recover files from a qnx4 filesystem >>>> on a harddrive. The hardrive has 6 partitions. I used the BOOT-CD and >>>> the photon file manager. If I do a df, it sees : >>>> >>>> /dev/hd0 >>>> /dev/hd0t77 >>>> /dev/hd0t77.1 >>>> /dev/hd0t77.2 >>>> /dev/hd0t77.3 >>>> /dev/hd0t77.4 >>>> /dev/hd0t77.5 >>>> >>>> If I try to mount /dev/hd0t77 or any of its declination, it says that >>>> the fs is corrupted. >>>> >>>> To my knowledge, the disk is not damaged. Do you see any reason for >>>> this message or any solution for me? >>>> >>>> Is there a way to fix the fs? >>>> >>>> Many thanks, >>>> >>>> david. >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> >>>> General >>>> http://community.qnx.com/sf/go/post93087 >>>> To cancel your subscription to this discussion, please e-mail >>>> general- filesystems-unsubscribe@community.qnx.com >>> >>> >>> >>> >>> _______________________________________________ >>> >>> General >>> http://community.qnx.com/sf/go/post93088 >>> To cancel your subscription to this discussion, please e-mail >>> general-filesystems-unsubscribe@community.qnx.com >> >> -- >> Prof. David Billard | David.Billard@hesge.ch >> University of Applied Sciences in Geneva | tel: +41 22 388 1885 >> Bât. F, 7 route de Drize - CH-1227 Carouge | fax: +41 22 388 1701 >> >> >> >> >> >> _______________________________________________ >> >> General >> http://community.qnx.com/sf/go/post93090 >> To cancel your subscription to this discussion, please e-mail general- >> filesystems-unsubscribe@community.qnx.com > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post93091 > To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com -- Prof. David Billard | David.Billard@hesge.ch University of Applied Sciences in Geneva | tel: +41 22 388 1885 Bât. F, 7 route de Drize - CH-1227 Carouge | fax: +41 22 388 1701 Tue, 15 May 2012 15:59:17 GMT http://community.qnx.com/sf/go/post93103 David Billard 2012-05-15T15:59:17Z http://community.qnx.com/sf/go/post93088 First thing to try is chkfsys, which is the QNX4 file system checker tool. If you don't want to make any changes to the disk, the -f option will prevent the tool from modifying anything. > -----Original Message----- > From: David Billard [mailto:community-noreply@qnx.com] > Sent: May-15-12 10:35 AM > To: general-filesystems > Subject: Mounting qnx4 fs with errors > > Dear all, > > I'm new to QNX. I would like to recover files from a qnx4 filesystem on a > harddrive. The hardrive has 6 partitions. I used the BOOT-CD and the photon > file manager. If I do a df, it sees : > > /dev/hd0 > /dev/hd0t77 > /dev/hd0t77.1 > /dev/hd0t77.2 > /dev/hd0t77.3 > /dev/hd0t77.4 > /dev/hd0t77.5 > > If I try to mount /dev/hd0t77 or any of its declination, it says that the fs is > corrupted. > > To my knowledge, the disk is not damaged. Do you see any reason for this > message or any solution for me? > > Is there a way to fix the fs? > > Many thanks, > > david. > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post93087 > To cancel your subscription to this discussion, please e-mail general- > filesystems-unsubscribe@community.qnx.com Tue, 15 May 2012 14:40:55 GMT http://community.qnx.com/sf/go/post93088 David Sarrazin 2012-05-15T14:40:55Z http://community.qnx.com/sf/go/post93091 What OS version are you running? Partition type 77 is normally reserved for partitions of type QNX4. Fdisk should say "QNX4" , simply because the type is 77. You can also try chkqnx6fs, on the off chance that the disks are formatted with the QNX6 file system. David > -----Original Message----- > From: David Billard [mailto:community-noreply@qnx.com] > Sent: May-15-12 10:33 AM > To: general-filesystems@community.qnx.com > Subject: Re: Mounting qnx4 fs with errors > > Hi David, > > it says that my partition is not a QNX4 fs. A rapid view with fdisk says > "unknown loader". Is there any way to detect which fs is on the partitions > (I'm almost sure it's qnx4, but perhaps am i wrong). > > many thanks, > > David. > > Le 15.05.2012 16:21, David Sarrazin a écrit : > > First thing to try is chkfsys, which is the QNX4 file system checker tool. If > you don't want to make any changes to the disk, the -f option will prevent > the tool from modifying anything. > > > >> -----Original Message----- > >> From: David Billard [mailto:community-noreply@qnx.com] > >> Sent: May-15-12 10:35 AM > >> To: general-filesystems > >> Subject: Mounting qnx4 fs with errors > >> > >> Dear all, > >> > >> I'm new to QNX. I would like to recover files from a qnx4 filesystem > >> on a harddrive. The hardrive has 6 partitions. I used the BOOT-CD and > >> the photon file manager. If I do a df, it sees : > >> > >> /dev/hd0 > >> /dev/hd0t77 > >> /dev/hd0t77.1 > >> /dev/hd0t77.2 > >> /dev/hd0t77.3 > >> /dev/hd0t77.4 > >> /dev/hd0t77.5 > >> > >> If I try to mount /dev/hd0t77 or any of its declination, it says that > >> the fs is corrupted. > >> > >> To my knowledge, the disk is not damaged. Do you see any reason for > >> this message or any solution for me? > >> > >> Is there a way to fix the fs? > >> > >> Many thanks, > >> > >> david. > >> > >> > >> > >> > >> _______________________________________________ > >> > >> General > >> http://community.qnx.com/sf/go/post93087 > >> To cancel your subscription to this discussion, please e-mail > >> general- filesystems-unsubscribe@community.qnx.com > > > > > > > > > > _______________________________________________ > > > > General > > http://community.qnx.com/sf/go/post93088 > > To cancel your subscription to this discussion, please e-mail > > general-filesystems-unsubscribe@community.qnx.com > > -- > Prof. David Billard | David.Billard@hesge.ch > University of Applied Sciences in Geneva | tel: +41 22 388 1885 > Bât. F, 7 route de Drize - CH-1227 Carouge | fax: +41 22 388 1701 > > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post93090 > To cancel your subscription to this discussion, please e-mail general- > filesystems-unsubscribe@community.qnx.com Tue, 15 May 2012 14:40:32 GMT http://community.qnx.com/sf/go/post93091 David Sarrazin 2012-05-15T14:40:32Z http://community.qnx.com/sf/go/post93090 Hi David, it says that my partition is not a QNX4 fs. A rapid view with fdisk says "unknown loader". Is there any way to detect which fs is on the partitions (I'm almost sure it's qnx4, but perhaps am i wrong). many thanks, David. Le 15.05.2012 16:21, David Sarrazin a écrit : > First thing to try is chkfsys, which is the QNX4 file system checker tool. If you don't want to make any changes to the disk, the -f option will prevent the tool from modifying anything. > >> -----Original Message----- >> From: David Billard [mailto:community-noreply@qnx.com] >> Sent: May-15-12 10:35 AM >> To: general-filesystems >> Subject: Mounting qnx4 fs with errors >> >> Dear all, >> >> I'm new to QNX. I would like to recover files from a qnx4 filesystem on a >> harddrive. The hardrive has 6 partitions. I used the BOOT-CD and the photon >> file manager. If I do a df, it sees : >> >> /dev/hd0 >> /dev/hd0t77 >> /dev/hd0t77.1 >> /dev/hd0t77.2 >> /dev/hd0t77.3 >> /dev/hd0t77.4 >> /dev/hd0t77.5 >> >> If I try to mount /dev/hd0t77 or any of its declination, it says that the fs is >> corrupted. >> >> To my knowledge, the disk is not damaged. Do you see any reason for this >> message or any solution for me? >> >> Is there a way to fix the fs? >> >> Many thanks, >> >> david. >> >> >> >> >> _______________________________________________ >> >> General >> http://community.qnx.com/sf/go/post93087 >> To cancel your subscription to this discussion, please e-mail general- >> filesystems-unsubscribe@community.qnx.com > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post93088 > To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com -- Prof. David Billard | David.Billard@hesge.ch University of Applied Sciences in Geneva | tel: +41 22 388 1885 Bât. F, 7 route de Drize - CH-1227 Carouge | fax: +41 22 388 1701 Tue, 15 May 2012 14:35:17 GMT http://community.qnx.com/sf/go/post93090 David Billard 2012-05-15T14:35:17Z http://community.qnx.com/sf/go/post93087 Dear all, I'm new to QNX. I would like to recover files from a qnx4 filesystem on a harddrive. The hardrive has 6 partitions. I used the BOOT-CD and the photon file manager. If I do a df, it sees : /dev/hd0 /dev/hd0t77 /dev/hd0t77.1 /dev/hd0t77.2 /dev/hd0t77.3 /dev/hd0t77.4 /dev/hd0t77.5 If I try to mount /dev/hd0t77 or any of its declination, it says that the fs is corrupted. To my knowledge, the disk is not damaged. Do you see any reason for this message or any solution for me? Is there a way to fix the fs? Many thanks, david. Tue, 15 May 2012 14:34:55 GMT http://community.qnx.com/sf/go/post93087 David Billard 2012-05-15T14:34:55Z http://community.qnx.com/sf/go/post92854 Smart information for disks behind RAID controller using QNX6.5.0 Hi all, Anybody familiar with getting smart information using QNX6.5.0. I am a newbie in this area. I want to get SMART information from disks behind a RAID controller. I have seen a project named smartmontools in sourceforge.net. But it is not supported for QNX in the case where the disks are behind RAID controller. Anyone please help me. Thanks a million, Honey S Tue, 01 May 2012 02:40:08 GMT http://community.qnx.com/sf/go/post92854 Honey S 2012-05-01T02:40:08Z http://community.qnx.com/sf/go/post92853 Hi all, I am a newbie in QNX. I am using QNX 6.5.0. I need to write a C++ program to find the sector size of a disk. I couldn't find any command/function for that. Please help me with a solution. Thanks in advance, Honey S Tue, 01 May 2012 02:36:43 GMT http://community.qnx.com/sf/go/post92853 Honey S 2012-05-01T02:36:43Z http://community.qnx.com/sf/go/post92674 Hi folks, There was some reset observed on the qnx device and it seems to be hardware reset. So what I see from system_info.txt file is that First case: Reset Cause = 0x00000500 Second case: Reset Cause = 0x00000508 May I know what does this reset cause mean and which component is causing the reset. Where do I find the mapping for all reset causes. Thanks n Regards, -------------------------- Satish Kumar Thakolam Software Defect Analyst - Radio Product Software - Germany - R&D Research In Motion Deutschland GmbH Office: +49 234 43 66 24 20 [cid:image001.gif@01CD1F18.61195A20] Fri, 20 Apr 2012 15:10:06 GMT http://community.qnx.com/sf/go/post92674 Satish kumar Thakolam 2012-04-20T15:10:06Z http://community.qnx.com/sf/go/post92621 No, I haven't written anything about waitfor() yet. Steve Reid (stever@qnx.com) Technical Editor QNX Software Systems -----Original Message----- From: Rohit Nair [mailto:community-noreply@qnx.com] Sent: Wednesday, April 18, 2012 2:02 PM To: general-filesystems Subject: Re: RE: C API similar to waitfor >PR 77631 is a laundry list of undocumented functions. You'll be happy to learn that waitfor() is on the list. Is this a document that is available on this website ? Can you link to it ? _______________________________________________ General http://community.qnx.com/sf/go/post92619 Wed, 18 Apr 2012 19:14:38 GMT http://community.qnx.com/sf/go/post92621 Steve Reid 2012-04-18T19:14:38Z http://community.qnx.com/sf/go/post92619 >PR 77631 is a laundry list of undocumented functions. You'll be happy to learn that waitfor() is on the list. Is this a document that is available on this website ? Can you link to it ? Wed, 18 Apr 2012 18:02:05 GMT http://community.qnx.com/sf/go/post92619 Rohit Nair 2012-04-18T18:02:05Z http://community.qnx.com/sf/go/post92610 PR 77631 is a laundry list of undocumented functions. You'll be happy to learn that waitfor() is on the list. Steve Reid (stever@qnx.com) Technical Editor QNX Software Systems -----Original Message----- From: Chris Travis [mailto:community-noreply@qnx.com] Sent: Wednesday, April 18, 2012 10:24 AM To: general-filesystems Subject: RE: C API similar to waitfor Sure, but according to our documentation and the "actual?" lib/c/qnx/waitfor.c it uses stat() :-) http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=/com.qnx.doc.neutrino_utilities/w/waitfor.html plus aside from the definition in libgen.c, waitfor() is not documented. :-( Wed, 18 Apr 2012 15:02:12 GMT http://community.qnx.com/sf/go/post92610 Steve Reid 2012-04-18T15:02:12Z http://community.qnx.com/sf/go/post92609 If waitfor() doesn't use poll, it is preferred. Which library includes waitfor()? Thanks for quick responses. -Chun Wed, 18 Apr 2012 14:36:02 GMT http://community.qnx.com/sf/go/post92609 Chun He 2012-04-18T14:36:02Z http://community.qnx.com/sf/go/post92608 waitfor() should be used so that when / if it's changed to not poll in a loop, everyone will benefit. -seanb On Wed, Apr 18, 2012 at 10:23:49AM -0400, Chris Travis wrote: > Sure, but according to our documentation and the "actual?" lib/c/qnx/waitfor.c it uses stat() :-) > http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=/com.qnx.doc.neutrino_utilities/w/waitfor.html > plus aside from the definition in libgen.c, waitfor() is not documented. :-( > > -----Original Message----- > From: Colin Burgess [mailto:community-noreply@qnx.com] > Sent: April-18-12 10:11 AM > To: general-filesystems > Subject: Re: C API similar to waitfor > > Actually it uses waitfor() - it's in libgen.h > > :-) > > On 12-04-18 10:05 AM, Chris Travis wrote: > > waitfor uses stat() > > > > Here is an example: > > > > int waitfor( char *path, unsigned wait_msec, unsigned wait_period_msec > > ) { > > struct stat sbuf; > > unsigned total = 0, ret; > > > > do { > > delay( wait_period_msec ); > > total += wait_period_msec; > > } while ( (ret = stat( path,&sbuf )) == -1&& total< wait_msec ); > > if ( total>= wait_msec ) > > errno = ETIMEDOUT; > > return ret; > > } > > > > Chris > > > > > > -----Original Message----- > > From: Chun He [mailto:community-noreply@qnx.com] > > Sent: April-18-12 2:39 AM > > To: general-filesystems > > Subject: C API similar to waitfor > > > > need to wait till a path (or a device node) to exists or appear in C program. > > Is there a C API equal to waitfor command? > > > > best regards, > > Chun > > > > > > > > _______________________________________________ > > > > General > > http://community.qnx.com/sf/go/post92596 > > > > > > > > > > _______________________________________________ > > > > General > > http://community.qnx.com/sf/go/post92605 > > > > -- > cburgess@qnx.com > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post92606 > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post92607 > Wed, 18 Apr 2012 14:33:06 GMT http://community.qnx.com/sf/go/post92608 Sean Boudreau 2012-04-18T14:33:06Z http://community.qnx.com/sf/go/post92607 Sure, but according to our documentation and the "actual?" lib/c/qnx/waitfor.c it uses stat() :-) http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=/com.qnx.doc.neutrino_utilities/w/waitfor.html plus aside from the definition in libgen.c, waitfor() is not documented. :-( -----Original Message----- From: Colin Burgess [mailto:community-noreply@qnx.com] Sent: April-18-12 10:11 AM To: general-filesystems Subject: Re: C API similar to waitfor Actually it uses waitfor() - it's in libgen.h :-) On 12-04-18 10:05 AM, Chris Travis wrote: > waitfor uses stat() > > Here is an example: > > int waitfor( char *path, unsigned wait_msec, unsigned wait_period_msec > ) { > struct stat sbuf; > unsigned total = 0, ret; > > do { > delay( wait_period_msec ); > total += wait_period_msec; > } while ( (ret = stat( path,&sbuf )) == -1&& total< wait_msec ); > if ( total>= wait_msec ) > errno = ETIMEDOUT; > return ret; > } > > Chris > > > -----Original Message----- > From: Chun He [mailto:community-noreply@qnx.com] > Sent: April-18-12 2:39 AM > To: general-filesystems > Subject: C API similar to waitfor > > need to wait till a path (or a device node) to exists or appear in C program. > Is there a C API equal to waitfor command? > > best regards, > Chun > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post92596 > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post92605 > -- cburgess@qnx.com _______________________________________________ General http://community.qnx.com/sf/go/post92606 Wed, 18 Apr 2012 14:23:48 GMT http://community.qnx.com/sf/go/post92607 Chris Travis 2012-04-18T14:23:48Z http://community.qnx.com/sf/go/post92606 Actually it uses waitfor() - it's in libgen.h :-) On 12-04-18 10:05 AM, Chris Travis wrote: > waitfor uses stat() > > Here is an example: > > int waitfor( char *path, unsigned wait_msec, unsigned wait_period_msec ) > { > struct stat sbuf; > unsigned total = 0, ret; > > do { > delay( wait_period_msec ); > total += wait_period_msec; > } while ( (ret = stat( path,&sbuf )) == -1&& total< wait_msec ); > if ( total>= wait_msec ) > errno = ETIMEDOUT; > return ret; > } > > Chris > > > -----Original Message----- > From: Chun He [mailto:community-noreply@qnx.com] > Sent: April-18-12 2:39 AM > To: general-filesystems > Subject: C API similar to waitfor > > need to wait till a path (or a device node) to exists or appear in C program. > Is there a C API equal to waitfor command? > > best regards, > Chun > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post92596 > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post92605 > -- cburgess@qnx.com Wed, 18 Apr 2012 14:10:31 GMT http://community.qnx.com/sf/go/post92606 Colin Burgess 2012-04-18T14:10:31Z http://community.qnx.com/sf/go/post92605 waitfor uses stat() Here is an example: int waitfor( char *path, unsigned wait_msec, unsigned wait_period_msec ) { struct stat sbuf; unsigned total = 0, ret; do { delay( wait_period_msec ); total += wait_period_msec; } while ( (ret = stat( path, &sbuf )) == -1 && total < wait_msec ); if ( total >= wait_msec ) errno = ETIMEDOUT; return ret; } Chris -----Original Message----- From: Chun He [mailto:community-noreply@qnx.com] Sent: April-18-12 2:39 AM To: general-filesystems Subject: C API similar to waitfor need to wait till a path (or a device node) to exists or appear in C program. Is there a C API equal to waitfor command? best regards, Chun _______________________________________________ General http://community.qnx.com/sf/go/post92596 Wed, 18 Apr 2012 14:04:59 GMT http://community.qnx.com/sf/go/post92605 Chris Travis 2012-04-18T14:04:59Z http://community.qnx.com/sf/go/post92596 need to wait till a path (or a device node) to exists or appear in C program. Is there a C API equal to waitfor command? best regards, Chun Wed, 18 Apr 2012 06:39:22 GMT http://community.qnx.com/sf/go/post92596 Chun He 2012-04-18T06:39:22Z http://community.qnx.com/sf/go/post92341 Dennis, where are you getting this from? The qnx6 file system is particlarily good for removable media, owing to its snapshot traansaction behavior. qnx4 file system should NOT be used if you have any requirement of file system consistency in the presence of media removes or sudden power off. ----- Original Message ----- From: Dennis Kellly [mailto:community-noreply@qnx.com] Sent: Wednesday, March 28, 2012 10:31 AM To: general-filesystems <post92323@community.qnx.com> Subject: Re: QNX 6 power fail-safe file system and compact flash cards You may find that qnx4fs is more reliable than qnx6fs with CF media. This suggestion is a result of a customer beta field test. Their failure rate was greatly reduced when they switched to qnx4fs... but you need to do your own testing! _______________________________________________ General http://community.qnx.com/sf/go/post92323 Thu, 29 Mar 2012 04:32:54 GMT http://community.qnx.com/sf/go/post92341 David Sarrazin 2012-03-29T04:32:54Z http://community.qnx.com/sf/go/post92339 >>> I'm also looking at fsync() and sync() and their notes about committing data. These should be effective immediately following fwrite() or write(). fwrite() can be more "at risk" than write() since there is an intermediate buffer. Use fdatasync() to force a flush of the intermediate buffer. You can also execute utility "sync" to force the disk io manager to flush all inodes, etc. But use caution as this is a relatively long operation, possibly impacting system timing. Thu, 29 Mar 2012 03:20:23 GMT http://community.qnx.com/sf/go/post92339 Dennis Kellly 2012-03-29T03:20:23Z http://community.qnx.com/sf/go/post92324 Great. We moved from the QNX 4 file system because it had the annoying habit of creating partial files on power fail. The consensus from QNX support and this forum was to use the QNX 6 file system. So for the benefit of anyone searching the forums for solutions to similar problems: DON'T USE THE QNX 6 FILESYSTEM UNLESS YOU HAVE ROTATING HARD DISKS. So, is there any guidance on making the QNX 4 filesystem more tolerant to power failure? Before I changed over, I was running chkfsys on powerup to clean broken files but this took time and didn't catch all the partial files. I'm also looking at fsync() and sync() and their notes about committing data. Any other suggestions? Wed, 28 Mar 2012 15:05:09 GMT http://community.qnx.com/sf/go/post92324 Robert Murrell 2012-03-28T15:05:09Z http://community.qnx.com/sf/go/post92323 You may find that qnx4fs is more reliable than qnx6fs with CF media. This suggestion is a result of a customer beta field test. Their failure rate was greatly reduced when they switched to qnx4fs... but you need to do your own testing! Wed, 28 Mar 2012 14:31:58 GMT http://community.qnx.com/sf/go/post92323 Dennis Kellly 2012-03-28T14:31:58Z http://community.qnx.com/sf/go/post92319 We are using the QNX 6 file system on a compact flash card. The card we are using does not meet the criteria for power fail safe recovery so we are using the "sync=optional" to get it to mount read/write. We had an unfortunate incident where a unit was powered off while writing a data file, and the boot image became truncated. We need to make the system power fail safe. We could tolerate a corrupted data file but not the boot image. This kind of failure can't be fixed in the field. I've tried several compact flash cards to find one that supports the file system, but this is a trial-and-error procedure. 1. Does anyone know of ANY compact flash card that fully supports the QNX 6 Power Fail Safe file system? 2. When will the QNX 6 file system be designed to support non-rotating media? Wed, 28 Mar 2012 12:30:18 GMT http://community.qnx.com/sf/go/post92319 Robert Murrell 2012-03-28T12:30:18Z http://community.qnx.com/sf/go/post92154 Is there a way to remove a named entry from /dev without actually detaching the resource manager? I would like to, depending on some trigger, make it appear like the resource manager doesn't exist. Unfortunately, the resource manager will lose its root privilege after attaching so I can't do a detach/attach all the time. Thanks, Steve Fri, 16 Mar 2012 19:48:57 GMT http://community.qnx.com/sf/go/post92154 Steve Inkpen 2012-03-16T19:48:57Z http://community.qnx.com/sf/go/post92147 Sir, Thanks for the earlier reply regarding bootable CD. Now things are done, but I am still stuck up with the problem. I am able to connect host and Target system, proof is in QNX target navigator I see QNX local host connected, I see a number of process, I am attaching a screen shot of it. I am not able to proceed further, if I want to access device on PCI bus how to proceed. Regards, Amit negi Fri, 16 Mar 2012 10:14:45 GMT http://community.qnx.com/sf/go/post92147 amit negi 2012-03-16T10:14:45Z http://community.qnx.com/sf/go/post92146 I have a resmgr at attached to /dev/bucase QNX 6.4.1 (x86) it has the next structure # ls /dev/bucase/* /dev/bucase/file1 /dev/bucase/test: f ff So when I use next sequence of calls after start of resmgr # echo /dev/bucase/* /dev/bucase/file1 /dev/bucase/test # echo /dev/bucase/test/* echo /dev/bucase/test/* /dev/bucase/test/f So second call to echo fails, cause I have two entries in test directory But ls /dev/bucase/test always work properly # ls /dev/bucase/test f ff Attaching minimum code with bug Problem doesn't occur when I comment string that frees reply buffer to MsgReply call. int handle_readdir(resmgr_context_t *ctp, io_read_t *msg, iofunc_ocb_t* ocb, struct myentry* entry){ char* reply = (char*)malloc(msg->i.nbytes); int rsize; //Cycle at directory entries rsize = (char*)de - reply; if (-1 == MsgReply(ctp->rcvid, rsize, realrep, rsize)){ perror("!!!!!readdir MsgReply"); } free(reply); //A comment of this string helps to avoid the problem but I cant clarify it (reply must be copied at the moment of its freeing, isnt it?) return _RESMGR_NOREPLY; } Fri, 16 Mar 2012 07:00:02 GMT http://community.qnx.com/sf/go/post92146 Michael Markov 2012-03-16T07:00:02Z http://community.qnx.com/sf/go/post91966 Hi , Thanks for the reply, things are done some issue with my pc Regards, Amit negi -----Original Message----- From: Dennis Kellly [mailto:community-noreply@qnx.com] Sent: Wednesday, March 07, 2012 5:59 PM To: general-filesystems Subject: Re: creating bootable cd of qnxsdp-6.5.0-201007091524-dvd Download the CD ISO ... rather than the DVD image? http://www.qnx.com/download/feature.html?programid=21182 _______________________________________________ General http://community.qnx.com/sf/go/post91936 Thu, 08 Mar 2012 04:15:18 GMT http://community.qnx.com/sf/go/post91966 amit negi 2012-03-08T04:15:18Z http://community.qnx.com/sf/go/post91936 Download the CD ISO ... rather than the DVD image? http://www.qnx.com/download/feature.html?programid=21182 Wed, 07 Mar 2012 12:28:34 GMT http://community.qnx.com/sf/go/post91936 Dennis Kellly 2012-03-07T12:28:34Z http://community.qnx.com/sf/go/post91929 please can anyone tell me the procedure to make a boot-able CD for QNX target Wed, 07 Mar 2012 06:25:27 GMT http://community.qnx.com/sf/go/post91929 amit negi 2012-03-07T06:25:27Z http://community.qnx.com/sf/go/post91803 Try adding "qnx6 sync=optional" to the end of your devb-xxx line. Apparently, your CF card responds truthfully that is does not support the "flush to disk" command required for qnx6fs. Mon, 27 Feb 2012 12:21:21 GMT http://community.qnx.com/sf/go/post91803 Dennis Kellly 2012-02-27T12:21:21Z http://community.qnx.com/sf/go/post91802 I installed QNX 6.5.0 on a CF with the QNX6 file system 179. I'm only able to mount this CF as "read only" in a QNX 6.5.0 Virtual Machine on my PC. Why is this? I would like to mount and copy some files to the image. I've done this in the past on QNX file system 79. Is there any solution/trick to do this? Mikael Mon, 27 Feb 2012 12:05:13 GMT http://community.qnx.com/sf/go/post91802 Mikael Eriksen 2012-02-27T12:05:13Z http://community.qnx.com/sf/go/post91629 chkqnx6fs could correct some type of corruptions, but most case(like this one), it is not possible. Could you provide the use info? You can get it by use -i `which -s fs-qnx6.so` Thanks yuxi Thu, 16 Feb 2012 06:28:41 GMT http://community.qnx.com/sf/go/post91629 Yuxi Zhang 2012-02-16T06:28:41Z http://community.qnx.com/sf/go/post91568 http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=/com.qnx.doc.neutrino_utilities/d/devb-umass.html http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=/com.qnx.doc.neutrino_user_guide/fsystems.html -----Original Message----- From: HuiHsien Wu [mailto:community-noreply@qnx.com] Sent: February-14-12 10:38 AM To: general-filesystems Subject: Re: RE: How to transfer a file from USB or Playbook? For usb stick. Not USB line. I just want to put a file to usb stick, and then plug-in the usb stick to QNX neutrino OS PC. Finally, copy the file from usb stick to other folder. Sorry, original description isn't clear. Thanks your attention. _______________________________________________ General http://community.qnx.com/sf/go/post91566 Tue, 14 Feb 2012 15:55:29 GMT http://community.qnx.com/sf/go/post91568 Chris Travis 2012-02-14T15:55:29Z http://community.qnx.com/sf/go/post91566 For usb stick. Not USB line. I just want to put a file to usb stick, and then plug-in the usb stick to QNX neutrino OS PC. Finally, copy the file from usb stick to other folder. Sorry, original description isn't clear. Thanks your attention. Tue, 14 Feb 2012 15:37:43 GMT http://community.qnx.com/sf/go/post91566 HuiHsien Wu 2012-02-14T15:37:43Z http://community.qnx.com/sf/go/post91565 You can do it to playbook - but not to an ordinary QNX host. For playbook, you use the blackberry application "Blackberry Device Manager" and a usb cable. Playbook file transfers are easier though using "explorer \\w.x.y.z" - i.e. wireless. :) Tue, 14 Feb 2012 15:34:00 GMT http://community.qnx.com/sf/go/post91565 Dennis Kellly 2012-02-14T15:34:00Z http://community.qnx.com/sf/go/post91564 > -----Message d'origine----- > De : HuiHsien Wu [mailto:community-noreply@qnx.com] > Envoyé : 14 février 2012 09:50 > À : general-filesystems > Objet : How to transfer a file from USB or Playbook? > > Problem: > I want to transfer a file from a Windows PC to a QNX neutrino PC by a USB. > Could not find a way to do this action. > That is not supported, even by Windows I think. I don`t think you can have to "master" devices. > Thank your support, > > > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post91557 > Tue, 14 Feb 2012 15:28:03 GMT http://community.qnx.com/sf/go/post91564 Mario Charest 2012-02-14T15:28:03Z http://community.qnx.com/sf/go/post91562 Rob Krten's book, The QNX Cookbook, includes code for a tar filesystem that you might find useful. Steve Reid (stever@qnx.com) Technical Editor QNX Software Systems -----Original Message----- From: Andrew Sherk [mailto:community-noreply@qnx.com] Sent: Tuesday, February 14, 2012 9:50 AM To: general-filesystems Subject: Re: Mount a zip file as a filesystem The deflate utility and inflator resource manager are documented here: http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=/com.qnx.doc.neutrino_utilities/d/deflate.html http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=/com.qnx.doc.neutrino_utilities/i/inflator.html -asherk > You are describing a "virtual filesystem". QNX provides two: inflator (see " > system architecture" guide) and pkgserver (used as an install tool). > > AFIK none exists for zip archives - though you could write one! > _______________________________________________ General http://community.qnx.com/sf/go/post91558 Tue, 14 Feb 2012 15:00:54 GMT http://community.qnx.com/sf/go/post91562 Steve Reid 2012-02-14T15:00:54Z http://community.qnx.com/sf/go/post91558 The deflate utility and inflator resource manager are documented here: http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=/com.qnx.doc.neutrino_utilities/d/deflate.html http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=/com.qnx.doc.neutrino_utilities/i/inflator.html -asherk > You are describing a "virtual filesystem". QNX provides two: inflator (see " > system architecture" guide) and pkgserver (used as an install tool). > > AFIK none exists for zip archives - though you could write one! > Tue, 14 Feb 2012 14:50:13 GMT http://community.qnx.com/sf/go/post91558 Andrew Sherk 2012-02-14T14:50:13Z http://community.qnx.com/sf/go/post91557 Problem: I want to transfer a file from a Windows PC to a QNX neutrino PC by a USB. Could not find a way to do this action. Thank your support, Tue, 14 Feb 2012 14:50:02 GMT http://community.qnx.com/sf/go/post91557 HuiHsien Wu 2012-02-14T14:50:02Z http://community.qnx.com/sf/go/post91524 You are describing a "virtual filesystem". QNX provides two: inflator (see "system architecture" guide) and pkgserver (used as an install tool). AFIK none exists for zip archives - though you could write one! Mon, 13 Feb 2012 14:58:20 GMT http://community.qnx.com/sf/go/post91524 Dennis Kellly 2012-02-13T14:58:20Z http://community.qnx.com/sf/go/post91522 Is there any way to mount a zip file as a read-only file system? Rather than copy and unzip, it would be really handy in my application to take a zip file on a USB drive and mount it as a file system. Unzipping would be done on-the-fly as files are read. Is there any way this can be done? Mon, 13 Feb 2012 14:42:05 GMT http://community.qnx.com/sf/go/post91522 Robert Murrell 2012-02-13T14:42:05Z http://community.qnx.com/sf/go/post91159 Hi all! I have EFS image, that obtained with the command mkefs. In QNX, it is possible to mount the images in different file systems (img, iso, qnx4) with, for example, the following sequence of commands: devb-loopback blk cache=128k,auto=none loopback fd=/tmp/q4.img mount -tqnx4 /dev/lo0 /q4flash How can i mount efs-image? Command "mount" requires to indicate filesystem type , but "mount" description (in utilities references) hasn't efs file system. or Is it required an alternative method? Thanks! Thu, 26 Jan 2012 06:48:53 GMT http://community.qnx.com/sf/go/post91159 Oleg Durandin 2012-01-26T06:48:53Z http://community.qnx.com/sf/go/post91053 > > Hello All, > > I have installed QNX 6.5 in Hard disk, and if i try to connect it to Hercules > II EBX SBC of P3 processor, it is showing one error, Invalid OS Image. It sounds like your Hercules BIOS is using a different drive translation. Have you checked the BIOS to see if there are settings for the translation? Maybe something like LBA or Large, etc. If not you would need to install the OS on the Hercules or board. Fri, 20 Jan 2012 17:17:43 GMT http://community.qnx.com/sf/go/post91053 Kevin Chiles 2012-01-20T17:17:43Z http://community.qnx.com/sf/go/post90951 Hello All, I have installed QNX 6.5 in Hard disk, and if i try to connect it to Hercules II EBX SBC of P3 processor, it is showing one error, Invalid OS Image. If I try to use the same hard disk to PC of processor P4, I am able to boot QNX Successfully. Could you please suggest us the way how do we boot using the same board. Waiting for your reply. Thanks, Dinakar. Tue, 17 Jan 2012 05:17:10 GMT http://community.qnx.com/sf/go/post90951 Dinakar Babu 2012-01-17T05:17:10Z http://community.qnx.com/sf/go/post90946 Hi Pavol No answer for your specific question (why fsysinfo reports writes on a R/O fs) but you should have a look at the QNX system profiler and check what processes are talking to the file-system driver. This would answer at least your real question (who is writing or trying to write to the filesystem). You can start from these pages if you have never used the system profiler before: http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=/com.qnx.doc.ide.userguide/topic/sysprof_INTRO_.html http://community.qnx.com/sf/wiki/do/viewPage/projects.ide/wiki/SystemProfiler Happy hunting, -- Mate From: Pavol Kycina <community-noreply@qnx.com<mailto:community-noreply@qnx.com>> Reply-To: <post90945@community.qnx.com<mailto:post90945@community.qnx.com>> Date: Mon, 16 Jan 2012 08:28:23 -0500 To: general-filesystems <post90945@community.qnx.com<mailto:post90945@community.qnx.com>> Subject: fsysinfo reports DISK I/O writes on read only filesystem Hello, I am trying to make small embedded system as power resilient as possible. That includes minimizing writes to storage medium. I have come across puzzling situation. I am trying to find the process which generates writes to one of the filesystems. These writes are reported by fsysinfo utility under DISK I/O write section. I have no clue which process it could be, so I mounted given filesystem as read-only in a hope, that offending process would report some kind of error. To my dismay fsysinfo continues to report disk i/o writes on this read-only filesystem. I have checked the read-only feature by trying to "touch file.txt", which failed. The filesystem in question is QNX6 one, OS version is x86 6.4.1. Any idea what's wrong? Thanks, PKY _______________________________________________ General http://community.qnx.com/sf/go/post90945 Mon, 16 Jan 2012 13:51:22 GMT http://community.qnx.com/sf/go/post90946 Mate Szarvas 2012-01-16T13:51:22Z http://community.qnx.com/sf/go/post90945 Hello, I am trying to make small embedded system as power resilient as possible. That includes minimizing writes to storage medium. I have come across puzzling situation. I am trying to find the process which generates writes to one of the filesystems. These writes are reported by fsysinfo utility under DISK I/O write section. I have no clue which process it could be, so I mounted given filesystem as read-only in a hope, that offending process would report some kind of error. To my dismay fsysinfo continues to report disk i/o writes on this read-only filesystem. I have checked the read-only feature by trying to "touch file.txt", which failed. The filesystem in question is QNX6 one, OS version is x86 6.4.1. Any idea what's wrong? Thanks, PKY Mon, 16 Jan 2012 13:28:22 GMT http://community.qnx.com/sf/go/post90945 Pavol Kycina 2012-01-16T13:28:22Z http://community.qnx.com/sf/go/post90875 Hello All , We are are running our system on QNX rtos , we have a amproboard LB 700 with compact flash as the boot disk and the harddisk for datalogging . In the middle of runnning our system the harddisk disappears , i.e df -P does not show hd1t79 , it only shows hd0t79 (compact flash) . When we look in the syslog , with sloginfo -w it is filled up with these errors repeating over and over Jan 09 13:54:34 2 5 0 scsi_interpret_sense: SK_ILLEGAL command 5a in databyte Jan 09 13:54:36 2 5 0 scsi_interpret_sense: path=1, target=1, lun=0, cam_status=c4, scsi_status=2 Jan 09 13:54:36 2 5 0 scsi_interpret_sense: error=70, sense=5, asc=2 4, ascq=0 Jan 09 13:54:36 2 5 0 scsi_interpret_sense: SK_ILLEGAL command 5a in databyte i gather briefly from the forums i.e means the harddisk is not detected by the driver, what i cannot see is how this is happening in the middle of the run .ie it starts up ok , starts logging the data and after a while ( may be 1 or 2 days) the above errors start showing up . When we reboot the system it comes up fine again . Any ideas / pointers to info are highly appreciated . Thanks & Regards -Subra Mon, 09 Jan 2012 20:18:38 GMT http://community.qnx.com/sf/go/post90875 Subra arya 2012-01-09T20:18:38Z http://community.qnx.com/sf/go/post90644 Stephan - We have used ETFS extensively under QNX 6.3.2 and 6.4.1. I don't have any experience with it under 6.5.0. We've used both 512 byte and 2K page NAND parts. We format our drives with a both a raw partition (for IPL boot) and a formatted partition. It has been very reliable and stable. The downside to ETFS - can't update raw partition from IPL (as you've discovered) - can't boot using UBoot or other boot loaders - limited support for large (4K page) NAND parts Even with the positive experience we've had thus far with ETFS, I would not recommend using it in a new design - if at all possible I'd use a managed NAND part. - Dan Thu, 15 Dec 2011 13:10:33 GMT http://community.qnx.com/sf/go/post90644 Dan Giorgis 2011-12-15T13:10:33Z http://community.qnx.com/sf/go/post90640 Hello, we consider to use QNX 6.5 with ETFS in a medical product. Our quality measures require to assess the level of quality for external (bought) software. As indicated in my previous post I searched the web for info on how to update the IPL/IFS in the raw partition with only few results (e.g. for etfsctl -p option). Because of this result I got the impression that ETFS is not heavily used - especially on NAND/QNX6.5. Is that true? What is your experience with ETFS, how reliable is it, how much is it used? Thanks a lot, - Stefan Thu, 15 Dec 2011 07:59:02 GMT http://community.qnx.com/sf/go/post90640 Stefan Koch 2011-12-15T07:59:02Z http://community.qnx.com/sf/go/post90639 Hello, on my project we will boot QNX 6.5 from NAND flash. Also the application is stored on NAND in the ETFS partition. For a test I have written the IPL/IFS at the beginning of the NAND memory with a programmer tool. Then I started the system and on the command line I created a ETFS structure on the NAND with a raw partition of 16MB. So far everything works fine - I can boot from NAND and I have my /fs/etfs mount for my application. My question: How can I update my IPL/IFS? From Google search I suspect that etfsctl can be used for this but I was not able to find a crisp explanation how to do it. What I have is my IPL/IFS binary and what I need is to program it to the beginning of my NAND including bad-block skipping. The IPL itself does reside in the first block which is considered to be free of bad blocks but the IFS (4MB) is not. I saw in my BSP that the IPL is able to skip bad blocks so everything makes basically sense - the missing thing is the update. Thanks for your advice, - Stefan Thu, 15 Dec 2011 07:47:01 GMT http://community.qnx.com/sf/go/post90639 Stefan Koch 2011-12-15T07:47:01Z http://community.qnx.com/sf/go/post90464 We have seen an issue where file system goes bad. Following is the error return code from qnx fs: fs-qnx6: / EBADFSYS (locate@blocks.c:936) After this, we get “Corrupted file system detected” error description. Following this file system becomes Read-only file system. This situation was observed while attempting to access/read files. How would QNX file system ensure that after detecting bad file system it does full file system recovery and allow access to these files again normally? Thanks Wed, 07 Dec 2011 13:50:25 GMT http://community.qnx.com/sf/go/post90464 Alex Karpov 2011-12-07T13:50:25Z http://community.qnx.com/sf/go/post90307 Hello, I just ran into the same problem. I use BSP for i.MX35 3DS, the MTD library shipped with this still contains that bug. I modified it accordingly and now I have write speed increased from 11KB/s (!!) to 70KB/s. Still not really satisfying, but might be that the flash part (RC28F256P33 from Numonyx) requires some special code. I downloaded bsp-freescale-p1022-ds-6.5.0.zip, which is only Sept 2011 released, and the MTD library shipped with this still contains that bug. Can you tell us the PR# for this issue and what the status is, please. We should much prefer to use an unmodified MTD library from QSS. Can the MTD library accessed separately anywhere? Thanks, Albrecht Sat, 26 Nov 2011 12:05:09 GMT http://community.qnx.com/sf/go/post90307 Albrecht Uhlmann 2011-11-26T12:05:09Z http://community.qnx.com/sf/go/post90082 Does ETFS support 4k NAND? If so, which BSP can I use to adapt the code from? Thanks. Tue, 15 Nov 2011 01:51:49 GMT http://community.qnx.com/sf/go/post90082 Alex Pavloff 2011-11-15T01:51:49Z http://community.qnx.com/sf/go/post89852 On Thu, 3 Nov 2011, Poul Christiansen wrote: > Hi > > I'm using the command line from the the SourceGuide page: > > svn checkout --username xxx@xxx.xxx http://community.qnx.com/svn/repos/filesystems/trunk > > with the proper username as used when logging in to foundry27. I see what you mean now. I'll double check but I know that some of the source code was removed from foundry a while back. Not sure if this was part of it or not. Peter Thu, 03 Nov 2011 12:39:24 GMT http://community.qnx.com/sf/go/post89852 Peter Martin 2011-11-03T12:39:24Z http://community.qnx.com/sf/go/post89850 Hi I'm using the command line from the the SourceGuide page: svn checkout --username xxx@xxx.xxx http://community.qnx.com/svn/repos/filesystems/trunk with the proper username as used when logging in to foundry27. Thu, 03 Nov 2011 12:06:17 GMT http://community.qnx.com/sf/go/post89850 Poul Christiansen 2011-11-03T12:06:17Z http://community.qnx.com/sf/go/post89849 Are you specifying that particular revision? What is the command line you are using for the check out? ----- Original Message ----- From: Poul Christiansen [mailto:community-noreply@qnx.com] Sent: Thursday, November 03, 2011 05:50 AM To: general-filesystems <post89848@community.qnx.com> Subject: Trouble downloading sources Hi I'm trying to download the sources as described in the SourceGuide - however the svn command fails: svn: No such revision 391412 I am sure I'm using the correct email address and password. I tried to log out and log out of foundry27 to check the password. How can I get the sources? Regards Poul Christiansen _______________________________________________ General http://community.qnx.com/sf/go/post89848 Thu, 03 Nov 2011 12:01:05 GMT http://community.qnx.com/sf/go/post89849 Peter Martin 2011-11-03T12:01:05Z http://community.qnx.com/sf/go/post89848 Hi I'm trying to download the sources as described in the SourceGuide - however the svn command fails: svn: No such revision 391412 I am sure I'm using the correct email address and password. I tried to log out and log out of foundry27 to check the password. How can I get the sources? Regards Poul Christiansen Thu, 03 Nov 2011 09:50:21 GMT http://community.qnx.com/sf/go/post89848 Poul Christiansen 2011-11-03T09:50:21Z http://community.qnx.com/sf/go/post89807 We're transferring a file system over the network to our system as a single file and want to unpack it into RAM for further processing. The documentation hints that we should be able to make up an EFS file system and use this with devf-ram. I can run devf-ram and it creates a file /tmp/fs1 but I'm unsure as to how to initialise this with the efs image. What is the correct sequence to mount an efs file using devf-ram? (along with flashctl?) As an alternative, we've discovered that tar appears to be able to create directories in /tmp. This goes against previous advice we've had that /dev/shmem doesn't support directories, and also with mkdir failing there. would this be a viable alternative? Regards Tue, 01 Nov 2011 17:49:08 GMT http://community.qnx.com/sf/go/post89807 Chris Trobridge 2011-11-01T17:49:08Z http://community.qnx.com/sf/go/post89461 Ok, here is what I get # flashctl -i -p /ram Array Info Total : 0x02000000 100% Chip Size : 0x02000000 100% Unit Size : 0x00010000 0% Part Info Total : 0x02000000 100% Spare : 0x00010000 0% Headers : 0x007D4494 24% Padding : 0x00023A55 0% Overhead : 0x00807EE9 25% Free : 0x0004E19C 0% Stale : 0x00ACE164 33% Avail. : 0x00B1C300 34% Reserved : 0x00000020 0% Unit Info Erase Stats Average : 0 Minimum : 0 Maximum : 2 Total : 437 And # df -kP Filesystem 1024-blocks Used Available Capacity Mounted on /dev/fs2p0 32704 21325 11378 66% /ram Not clear to me how the breakdown from flashctl tallies up to 100% and why Free is 0%. Can you point to some docs that explain the breakdown? Thanks Wed, 19 Oct 2011 17:59:14 GMT http://community.qnx.com/sf/go/post89461 Robert D'Attilio 2011-10-19T17:59:14Z http://community.qnx.com/sf/go/post89460 Try flashctl -i -p /ram to see the breakdown of free space/stale space/used space, and overhead. > -----Original Message----- > From: Robert D'Attilio [mailto:community-noreply@qnx.com] > Sent: October-19-11 1:25 PM > To: general-filesystems > Subject: Re: RE: Ram disk free space does not align with what is > actually being reported by ls -l > > Tried that already and there are no extra (hidden) files. > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post89459 Wed, 19 Oct 2011 17:33:06 GMT http://community.qnx.com/sf/go/post89460 David Sarrazin 2011-10-19T17:33:06Z http://community.qnx.com/sf/go/post89459 Tried that already and there are no extra (hidden) files. Wed, 19 Oct 2011 17:24:56 GMT http://community.qnx.com/sf/go/post89459 Robert D'Attilio 2011-10-19T17:24:56Z http://community.qnx.com/sf/go/post89457 Try ls -al to show any hidden files starting with '.' ... maybe there is more content on the disk. -----Original Message----- From: Robert D'Attilio [mailto:community-noreply@qnx.com] Sent: October-19-11 12:41 PM To: general-filesystems Subject: Ram disk free space does not align with what is actually being reported by ls -l Hi: We are using QNX641 (PowerPC version) and have created a 32M ram disk using the following commands: devf-ram -i 2 -s0,32M & waitfor /dev/fs2p0 flashctl -p /dev/fs2p0 -e -f -n /ram -m Running 'df -kP' immediately followed by 'ls -l': # df -kP Filesystem 1024-blocks Used Available Capacity Mounted on /dev/fs2p0 32704 25291 7412 78% /ram # ls -l total 34203 -rw-r--r-- 1 1000 1000 172 Aug 29 20:36 .lldpport.conf -rw-r--r-- 1 root 0 41 Oct 18 16:35 lldp-debug -rw-r--r-- 1 root 0 953 Oct 18 16:35 plm-debug -rw-r--r-- 1 root 0 2657904 Oct 19 11:26 slc-ew-debug -rw-r--r-- 1 root 0 3145819 Oct 19 10:13 slc-ew-debug.1_2011-10-19-11-26 -rw-r--r-- 1 root 0 3145816 Oct 19 06:48 slc-ew-debug.2_2011-10-19-10-13 -rw-r--r-- 1 root 0 2267346 Oct 19 11:34 slc-we-debug -rw-r--r-- 1 root 0 3145728 Oct 19 10:18 slc-we-debug.1_2011-10-19-11-34 -rw-r--r-- 1 root 0 3145728 Oct 19 07:03 slc-we-debug.2_2011-10-19-10-18 So 'df' reports ~25M of disk space is used yet if you tally up the contents of the directory as reported by ls -l, only ~17M are used. Not clear why the discrepancy? I can understand that there might be some overhead for the actual management of the partition but 8M?? Thanks Robert _______________________________________________ General http://community.qnx.com/sf/go/post89456 Wed, 19 Oct 2011 17:10:33 GMT http://community.qnx.com/sf/go/post89457 Peter Martin 2011-10-19T17:10:33Z http://community.qnx.com/sf/go/post89456 Hi: We are using QNX641 (PowerPC version) and have created a 32M ram disk using the following commands: devf-ram -i 2 -s0,32M & waitfor /dev/fs2p0 flashctl -p /dev/fs2p0 -e -f -n /ram -m Running 'df -kP' immediately followed by 'ls -l': # df -kP Filesystem 1024-blocks Used Available Capacity Mounted on /dev/fs2p0 32704 25291 7412 78% /ram # ls -l total 34203 -rw-r--r-- 1 1000 1000 172 Aug 29 20:36 .lldpport.conf -rw-r--r-- 1 root 0 41 Oct 18 16:35 lldp-debug -rw-r--r-- 1 root 0 953 Oct 18 16:35 plm-debug -rw-r--r-- 1 root 0 2657904 Oct 19 11:26 slc-ew-debug -rw-r--r-- 1 root 0 3145819 Oct 19 10:13 slc-ew-debug.1_2011-10-19-11-26 -rw-r--r-- 1 root 0 3145816 Oct 19 06:48 slc-ew-debug.2_2011-10-19-10-13 -rw-r--r-- 1 root 0 2267346 Oct 19 11:34 slc-we-debug -rw-r--r-- 1 root 0 3145728 Oct 19 10:18 slc-we-debug.1_2011-10-19-11-34 -rw-r--r-- 1 root 0 3145728 Oct 19 07:03 slc-we-debug.2_2011-10-19-10-18 So 'df' reports ~25M of disk space is used yet if you tally up the contents of the directory as reported by ls -l, only ~17M are used. Not clear why the discrepancy? I can understand that there might be some overhead for the actual management of the partition but 8M?? Thanks Robert Wed, 19 Oct 2011 16:41:18 GMT http://community.qnx.com/sf/go/post89456 Robert D'Attilio 2011-10-19T16:41:18Z http://community.qnx.com/sf/go/post89376 Martin, You'll need to modify the "struct spare" in hardware/etfs/nand2048/<boardname>/devio.h That structure has to match the layout of the spare area that is dicated by the hardware. The structure normally will contain things like the base etfs_trans (fid, seqno,cluster), plus a CRC or ECC. The default 64-byte structure is only for use with software 1-bit ECC, so the fields have been packed without regard for the hardware layout. If your device supports hardware ECC (anything stronger than 1-bit will require hardware support), then you'll need to modify the structure layout to put the ECC fields at the offsets that the hardware describes for that controller. Once that is done, devio_readtrans(), devio_readcluster(), devio_postcluster() have to be modified to work with the new structure. > Sorry got it wrong (2048byte + 64 byte is correct). > But nearly all the bigger NAND devices e.g. from Micron (>=16Gbit) have a page > size of 4096byte + 224byte. The question remains the same what must be done > to get those running? > > Martin Thu, 13 Oct 2011 15:45:12 GMT http://community.qnx.com/sf/go/post89376 David Sarrazin 2011-10-13T15:45:12Z http://community.qnx.com/sf/go/post89331 Sorry got it wrong (2048byte + 64 byte is correct). But nearly all the bigger NAND devices e.g. from Micron (>=16Gbit) have a page size of 4096byte + 224byte. The question remains the same what must be done to get those running? Martin Wed, 12 Oct 2011 13:39:47 GMT http://community.qnx.com/sf/go/post89331 Martin Reichherzer 2011-10-12T13:39:47Z http://community.qnx.com/sf/go/post89328 Hello, I'm in search for information that helps me to select a apropriate NAND device for a new design. We would like to have a NAND size of at least 16Gbit/2GB. Processors we are planning to use are: - i.Mx53: there is a QNX driver in the i.MX53EVK BSP (for 2048Byte + 64Byte page size) -P2020: there is also a driver available but only for 512Byte page size. According to the QNX help article about system limits there is no ECC support for 512 Byte size. Is this right? Regarding the newer Micron NAND devices, all seem to have a page size of 2048byte + 96byte (not 64byte). What would be necessary to get those devices running with the drivers mentioned above. Is there documentation available regarding those adoptions? Is there a documentation for lib-etfs? Thanks Martin Wed, 12 Oct 2011 12:56:58 GMT http://community.qnx.com/sf/go/post89328 Martin Reichherzer 2011-10-12T12:56:58Z http://community.qnx.com/sf/go/post88916 David, That was it. Thanks for the quick reply. Rex Fri, 16 Sep 2011 21:39:20 GMT http://community.qnx.com/sf/go/post88916 Rex Lam 2011-09-16T21:39:20Z http://community.qnx.com/sf/go/post88903 Rex, This error message means that chkqnx6fs thinks the Filesystem you've told it to check is mounted read-write. If you re-mount that Filesystem as read-only "mount -ur <mntpnt>", does chkqnx6fs work correctly? David > -----Original Message----- > From: Rex Lam [mailto:community-noreply@qnx.com] > Sent: September-16-11 1:54 PM > To: general-filesystems > Subject: chkqnx6fs problem? > > We have encountered a problem using chkqnx6fs on 250GB drives. We have > tested this on three Hitachi 250GB drives and one Seagate 250GB drive. > It returns this: "error: potentially unstable filessytem", and fails > to check the drive. It works great on 80GB drives. Is there a problem > with the chkqnx6fs utility? > > Hard drives are configured in AHCI mode, and partitioned and formatted > with qnx6 filesystem. > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post88902 Fri, 16 Sep 2011 18:02:29 GMT http://community.qnx.com/sf/go/post88903 David Sarrazin 2011-09-16T18:02:29Z http://community.qnx.com/sf/go/post88902 We have encountered a problem using chkqnx6fs on 250GB drives. We have tested this on three Hitachi 250GB drives and one Seagate 250GB drive. It returns this: "error: potentially unstable filessytem", and fails to check the drive. It works great on 80GB drives. Is there a problem with the chkqnx6fs utility? Hard drives are configured in AHCI mode, and partitioned and formatted with qnx6 filesystem. Fri, 16 Sep 2011 17:54:06 GMT http://community.qnx.com/sf/go/post88902 Rex Lam 2011-09-16T17:54:06Z http://community.qnx.com/sf/go/post88091 The system seems to boot with ipl-diskpc2, but its coming up read-only with Compact Flash cards I have here. Fri, 12 Aug 2011 20:53:29 GMT http://community.qnx.com/sf/go/post88091 Robert Murrell 2011-08-12T20:53:29Z http://community.qnx.com/sf/go/post88089 Where do I get the secondary boot loader ipl-diskpc2-fsq6? It doesn't come with the QNX 6.5.0 distribution. Only ipl-diskpc2 and ipl-diskpc2-flop are provided. Fri, 12 Aug 2011 19:42:47 GMT http://community.qnx.com/sf/go/post88089 Robert Murrell 2011-08-12T19:42:47Z http://community.qnx.com/sf/go/post88087 From the driver expert: It is translated to an IDE Flush Cache command (0xe7 or 0xea). Most of the commands from the filesystem are using SCSI CAM terminology. > -----Original Message----- > From: Robert Murrell [mailto:community-noreply@qnx.com] > Sent: August-12-11 3:10 PM > To: general-filesystems > Subject: Re: RE: RE: RE: Partial files being create? > > Is there a generic or standard terminology for SC_SYNC? What property > should I be asking for from Compact Flash manufacturers? > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post88086 Fri, 12 Aug 2011 19:17:19 GMT http://community.qnx.com/sf/go/post88087 David Sarrazin 2011-08-12T19:17:19Z http://community.qnx.com/sf/go/post88086 Is there a generic or standard terminology for SC_SYNC? What property should I be asking for from Compact Flash manufacturers? Fri, 12 Aug 2011 19:10:11 GMT http://community.qnx.com/sf/go/post88086 Robert Murrell 2011-08-12T19:10:11Z http://community.qnx.com/sf/go/post88085 We will likely switch to the QNX 6 file system if we can be assured that we can get Compact Flash cards that support thei SC_SYNC operation. If we have to stay with QNX 4, I can increase the reliability by not writing the image header until the last block is written to the file. The secondary boot loader will detect this condition and can accommodate it. Fri, 12 Aug 2011 18:48:30 GMT http://community.qnx.com/sf/go/post88085 Robert Murrell 2011-08-12T18:48:30Z http://community.qnx.com/sf/go/post88084 If running chkfsys is okay, then you should be good. I'm trying to think of cases that chkfsys can't repair, but nothing comes to mind. If you can handle truncated files, then you should be okay. Your original post made it sound like you couldn't tolerate any form of corruption to the /.boot or /.altboot files. QNX6 filesystem is still the best way to guarantee that the file is either 100% the old content, or 100% the new content, but if you can handle the partial write case, then keep what you have. > -----Original Message----- > From: Robert Murrell [mailto:community-noreply@qnx.com] > Sent: August-12-11 1:35 PM > To: general-filesystems > Subject: Re: RE: RE: Partial files being create? > > This just keeps getting better. It took me months to get the source > code for ipl-diskpc2. Before I turn the rudder to the Titanic and > switch to QNX 6, I need to understand the power-fail errors that the > QNX 4 file system is susceptible to. I can work around lost data and > partial files. Are there any potential errors that can't be fixed by > chkfsys? > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post88082 Fri, 12 Aug 2011 18:35:13 GMT http://community.qnx.com/sf/go/post88084 David Sarrazin 2011-08-12T18:35:13Z http://community.qnx.com/sf/go/post88082 This just keeps getting better. It took me months to get the source code for ipl-diskpc2. Before I turn the rudder to the Titanic and switch to QNX 6, I need to understand the power-fail errors that the QNX 4 file system is susceptible to. I can work around lost data and partial files. Are there any potential errors that can't be fixed by chkfsys? Fri, 12 Aug 2011 17:35:16 GMT http://community.qnx.com/sf/go/post88082 Robert Murrell 2011-08-12T17:35:16Z http://community.qnx.com/sf/go/post88080 Lost clusters under FAT are the same problem, the file is not complete/incorrect. It's not possible to recover those clusters if the boot image is damaged. A colleague brought up a good point. The QNX6 file system already ensures that /.boot and /.altboot will never be partially written, by implicitly doing the "+hold". All other files require the chattr command. Yes, there's a new second-stage IPL required (diskpc2-fsq6) for the QNX6 file system. The "required properties" question. The QNX6 file system is, above all else, supposed to guarantee power-loss reliability. As a result, it queries the hardware to see if an SC_SYNC operation is supported. If the hardware says that it is not, then the filesystem will not mount read-write, since it can't guarantee that when it asks for data to be flushed, the hardware will comply. Some CF cards do work, and some don't. Some lie and say that the support the command when they really don't. If you want to avoid this check, pass "-o sync=optional" to the mount command, and the filesystem will mount read-write, even if the hardware doesn't claim to support SC_SYNC. David > -----Original Message----- > From: Robert Murrell [mailto:community-noreply@qnx.com] > Sent: August-12-11 11:28 AM > To: general-filesystems > Subject: Re: RE: Partial files being create? > > Great. This isn't a problem under FAT file systems, other than lost > clusters which are easily recovered. > > Now for the next questions: > > Does the QNX 6 filesystem need a new IPL? We are using a custom ipl- > diskpc2. > > It looks like I use the devctl function to programmatically do what > chattr is doing. Is there any guidance on how to set/clear this hold > flag using devctl? > > The section on "Required properties of the device" is unclear. Will > the QNX 6 filesystem work with a Compact Flash card? > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post88076 Fri, 12 Aug 2011 17:09:24 GMT http://community.qnx.com/sf/go/post88080 David Sarrazin 2011-08-12T17:09:24Z http://community.qnx.com/sf/go/post88077 > Is there any guidance on how to set/clear this hold flag using devctl? There is a sample here: http://www.qnx.com/developers/docs/6.4.1/neutrino/user_guide/fsystems.html#Q NX6_snapshots On 11-08-12 11:27 AM, "Robert Murrell" <community-noreply@qnx.com> wrote: > Great. This isn't a problem under FAT file systems, other than lost clusters > which are easily recovered. > > Now for the next questions: > > Does the QNX 6 filesystem need a new IPL? We are using a custom ipl-diskpc2. > > It looks like I use the devctl function to programmatically do what chattr is > doing. Is there any guidance on how to set/clear this hold flag using devctl? > > The section on "Required properties of the device" is unclear. Will the QNX 6 > filesystem work with a Compact Flash card? > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post88076 > Fri, 12 Aug 2011 15:34:49 GMT http://community.qnx.com/sf/go/post88077 Mate Szarvas 2011-08-12T15:34:49Z http://community.qnx.com/sf/go/post88076 Great. This isn't a problem under FAT file systems, other than lost clusters which are easily recovered. Now for the next questions: Does the QNX 6 filesystem need a new IPL? We are using a custom ipl-diskpc2. It looks like I use the devctl function to programmatically do what chattr is doing. Is there any guidance on how to set/clear this hold flag using devctl? The section on "Required properties of the device" is unclear. Will the QNX 6 filesystem work with a Compact Flash card? Fri, 12 Aug 2011 15:27:58 GMT http://community.qnx.com/sf/go/post88076 Robert Murrell 2011-08-12T15:27:58Z http://community.qnx.com/sf/go/post88075 The QNX4 file system is documented as not being power-safe. You can get corrupted files, or partial files if power is removed during writing. This is exactly what the QNX6 power-safe file system was created to address. Even in the QNX6 file system, if you are performing a series of write() calls to write the data, you can still get a partial file if you remove power after some write() calls have completed. However, on the QNX6 file system, there is a solution: chattr +hold / <copy your /.boot file> chattr -hold / The "chattr +hold/chattr -hold" commands lock-out the QNX6 file system's "snapshot" operation. On QNX6, a snapshot changes the current file system working view into a committed view on disk. By bracketing your file operation with that, you can ensure atomicity. This is documented here: http://www.qnx.com/developers/docs/6.5.0/topic/com.qnx.doc.neutrino_sys_ arch/fsys.html?path=13_9_9_6_2#QNX6_performance David > -----Original Message----- > From: Robert Murrell [mailto:community-noreply@qnx.com] > Sent: August-12-11 10:13 AM > To: general-filesystems > Subject: Partial files being create? > > I found an unexpected and disturbing issue relating to the QNX 4 file > system. When writing to a file, and then powering down during the > write, on powerup a partial file is created! I was expecting the file > name to be present, but with a zero length. I would expect that NONE > of the data written to the file would be committed until the file was > closed. Unfortunately, my program was writing to /.boot at the time of > the powerdown. On repowering, the IPL finds the image signature in the > first 8Kbytes, thinks its good, loads and executes it. > > In our application, the system must be tolerant of unexpected > powerdowns. I'm developing under QNX 6.5.0 and using the low-level C > open-write-close functions. Is there a way to prevent partial files > under this condition? > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post88066 Fri, 12 Aug 2011 15:01:39 GMT http://community.qnx.com/sf/go/post88075 David Sarrazin 2011-08-12T15:01:39Z http://community.qnx.com/sf/go/post88066 I found an unexpected and disturbing issue relating to the QNX 4 file system. When writing to a file, and then powering down during the write, on powerup a partial file is created! I was expecting the file name to be present, but with a zero length. I would expect that NONE of the data written to the file would be committed until the file was closed. Unfortunately, my program was writing to /.boot at the time of the powerdown. On repowering, the IPL finds the image signature in the first 8Kbytes, thinks its good, loads and executes it. In our application, the system must be tolerant of unexpected powerdowns. I'm developing under QNX 6.5.0 and using the low-level C open-write-close functions. Is there a way to prevent partial files under this condition? Fri, 12 Aug 2011 14:13:27 GMT http://community.qnx.com/sf/go/post88066 Robert Murrell 2011-08-12T14:13:27Z http://community.qnx.com/sf/go/post87793 Or you could do(as root) chmod -s /usr/sbin/op and use op to run commands as root. ----- Original Message ----- From: David Sarrazin [mailto:community-noreply@qnx.com] Sent: Wednesday, August 03, 2011 08:51 AM To: general-filesystems <post87790@community.qnx.com> Subject: Re: Unable to run fs-cifs unless I'm root Fs-cifs is trying to do resmgr_attach(), which requires uid=0. The simple solution is make "on" setuid, then invoke fs-cifs as "on fs-cifs". David On 2011-08-03, at 7:33 AM, "Glenn Schmottlach" <community-noreply@qnx.com> wrote: > I'm having problems running fs-cifs unless I'm logged in as "root". If I'm "root" then launching fs-cifs works fine and I can attach to my PC. If I create a user account and I run fs-cifs using non-root credentials get the following error: > > $ fs-cifs > Unable to register for mount requests. Operation not permitted > > I added my account to all the same groups that root is a member of: > > $id > uid=100(gschmott) gid=4(adm) groups=0(root),1(bin),2(daemon),3(sys),4(adm),5(tty) > > Still no luck. It's probably a permissions issue but I'm struggling to figure out how to fix it. Can anyone offer some suggestions? > > Thanks . . . > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post87783 > _______________________________________________ General http://community.qnx.com/sf/go/post87790 Wed, 03 Aug 2011 16:11:51 GMT http://community.qnx.com/sf/go/post87793 Chris Travis 2011-08-03T16:11:51Z http://community.qnx.com/sf/go/post87790 Fs-cifs is trying to do resmgr_attach(), which requires uid=0. The simple solution is make "on" setuid, then invoke fs-cifs as "on fs-cifs". David On 2011-08-03, at 7:33 AM, "Glenn Schmottlach" <community-noreply@qnx.com> wrote: > I'm having problems running fs-cifs unless I'm logged in as "root". If I'm "root" then launching fs-cifs works fine and I can attach to my PC. If I create a user account and I run fs-cifs using non-root credentials get the following error: > > $ fs-cifs > Unable to register for mount requests. Operation not permitted > > I added my account to all the same groups that root is a member of: > > $id > uid=100(gschmott) gid=4(adm) groups=0(root),1(bin),2(daemon),3(sys),4(adm),5(tty) > > Still no luck. It's probably a permissions issue but I'm struggling to figure out how to fix it. Can anyone offer some suggestions? > > Thanks . . . > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post87783 > Wed, 03 Aug 2011 12:51:03 GMT http://community.qnx.com/sf/go/post87790 David Sarrazin 2011-08-03T12:51:03Z http://community.qnx.com/sf/go/post87783 I'm having problems running fs-cifs unless I'm logged in as "root". If I'm "root" then launching fs-cifs works fine and I can attach to my PC. If I create a user account and I run fs-cifs using non-root credentials get the following error: $ fs-cifs Unable to register for mount requests. Operation not permitted I added my account to all the same groups that root is a member of: $id uid=100(gschmott) gid=4(adm) groups=0(root),1(bin),2(daemon),3(sys),4(adm),5(tty) Still no luck. It's probably a permissions issue but I'm struggling to figure out how to fix it. Can anyone offer some suggestions? Thanks . . . Wed, 03 Aug 2011 11:32:46 GMT http://community.qnx.com/sf/go/post87783 Glenn Schmottlach 2011-08-03T11:32:46Z http://community.qnx.com/sf/go/post87164 If you have a support plan with QNX and would like a fix for 6.4.1 procnto, you could open a case for this issue through the support plan. In which case, please include a link to this posting so the person who gets the case can sync up with me. http://community.qnx.com/sf/go/post87113 Best regards, asherk -----Original Message----- From: Markus Schmoelzer [mailto:community-noreply@qnx.com] Sent: Wednesday, July 06, 2011 4:09 AM To: general-filesystems Subject: Re: RE: readdir() sets wrong dirent->d_namelen value? Thanks for the hint. Using your program, I made the similar observations on my target: Some of the directories are processed properly, others aren't. Some results differ from yours, but that was to expect. Unfortunately I don't have the opportunity to check whether it works fine on 6.5 - let alone upgrading to that version right now. Anyway, I'll try to get around using 'd_namelen' wherever possible. Using 'strlen(d_name)' instead seems safe, of course. Yet, there is a small performance price to pay which is why this solution is not entirely satisfying for me. Nevertheless, thanks for your support. _______________________________________________ General http://community.qnx.com/sf/go/post87113 Wed, 06 Jul 2011 20:22:06 GMT http://community.qnx.com/sf/go/post87164 Andrew Sherk 2011-07-06T20:22:06Z http://community.qnx.com/sf/go/post87113 Thanks for the hint. Using your program, I made the similar observations on my target: Some of the directories are processed properly, others aren't. Some results differ from yours, but that was to expect. Unfortunately I don't have the opportunity to check whether it works fine on 6.5 - let alone upgrading to that version right now. Anyway, I'll try to get around using 'd_namelen' wherever possible. Using 'strlen(d_name)' instead seems safe, of course. Yet, there is a small performance price to pay which is why this solution is not entirely satisfying for me. Nevertheless, thanks for your support. Wed, 06 Jul 2011 08:09:00 GMT http://community.qnx.com/sf/go/post87113 Markus Kohler 2011-07-06T08:09:00Z http://community.qnx.com/sf/go/post87073 I think the behavior depends on the process that populates the dirent fields for the given path you are querying. For example, try out the following test. The d_namelen values are correct for "/bin" but incorrect for "/proc/boot" (like what you are seeing). #include <stdio.h> #include <dirent.h> #include <stdlib.h> #include <string.h> int printdir(char* path) { DIR* dirp; struct dirent* direntp; printf("\ncontents of %s\n", path); dirp = opendir( path ); if( dirp != NULL ) { for(;;) { direntp = readdir( dirp ); if( direntp == NULL ) break; printf( "\"%s\", %d, %d\n", direntp->d_name, direntp->d_namelen, strlen(direntp->d_name) ); } closedir( dirp ); return EXIT_SUCCESS; } return EXIT_FAILURE; } int main( void ) { printdir("/proc/boot"); return printdir("/bin"); } Running on an x86 6.4.1 installation in vmware: contents of /proc/boot "startup-script", 15, 14 "unlink_list", 12, 11 "procnto-smp-instr", 18, 17 "libc.so.3", 10, 9 "libc.so", 8, 7 etc. contents of /bin ".", 1, 1 "..", 2, 2 "ap", 2, 2 "aps", 3, 3 "asa", 3, 3 "cat", 3, 3 "chgrp", 5, 5 "chmod", 5, 5 "chown", 5, 5 "confstr", 7, 7 etc. Note, however, when I try the same test on a 6.5.0 x86 installation, the direntp->d_namelen are ok for /proc/boot. Regards, asherk -----Original Message----- From: Markus Schmoelzer [mailto:community-noreply@qnx.com] Sent: Friday, July 01, 2011 8:37 AM To: general-filesystems Subject: readdir() sets wrong dirent->d_namelen value? Hi everybody, as written in the QNX documentation on "struct dirent", the "d_namelen" member holds the number of characters of the directory entry name, stored in the "d_name" member (not regarding the terminating '\0'). I'm using QNX 6.4.1 on an embedded PPC target. My problem is, that the string length of "d_name" is actually 1 character less than "d_namelen" indicates (e.g. a directory entry named "bitmaps" has a "d_namelen" value of 8 instead of 7). Is this a flaw in QNX 6.4.1, or is there a reasonable explanation to this? One could be, that "d_namelen" in fact regards the terminating '\0', or it accounts for a preceeding '/' character (which is however not stored in the "d_name" member of the dirent struct)... I would appreciate any comments on this matter. Many thanks in advance! _______________________________________________ General http://community.qnx.com/sf/go/post87017 Tue, 05 Jul 2011 14:52:49 GMT http://community.qnx.com/sf/go/post87073 Andrew Sherk 2011-07-05T14:52:49Z http://community.qnx.com/sf/go/post87017 Hi everybody, as written in the QNX documentation on "struct dirent", the "d_namelen" member holds the number of characters of the directory entry name, stored in the "d_name" member (not regarding the terminating '\0'). I'm using QNX 6.4.1 on an embedded PPC target. My problem is, that the string length of "d_name" is actually 1 character less than "d_namelen" indicates (e.g. a directory entry named "bitmaps" has a "d_namelen" value of 8 instead of 7). Is this a flaw in QNX 6.4.1, or is there a reasonable explanation to this? One could be, that "d_namelen" in fact regards the terminating '\0', or it accounts for a preceeding '/' character (which is however not stored in the "d_name" member of the dirent struct)... I would appreciate any comments on this matter. Many thanks in advance! Fri, 01 Jul 2011 12:37:12 GMT http://community.qnx.com/sf/go/post87017 Markus Kohler 2011-07-01T12:37:12Z http://community.qnx.com/sf/go/post86764 Dennis! Thanks for your suggestion, let me think in the direction which you have proposed. Wed, 22 Jun 2011 04:06:53 GMT http://community.qnx.com/sf/go/post86764 Lavin Pottekkat 2011-06-22T04:06:53Z http://community.qnx.com/sf/go/post86743 Short of using pps - which requires very "special" files - the only way to detect normal file changes is to create a resource manager and attach to the "root" of the namespace you want to watch. You can then register handlers for any of the _IO_* messages you want to "see" ( maybe _IO_OPEN, _IO_CLOSE_OCB and _IO_CLOSE_DUP?) The handler(s) you create in the resource manager must have some mechanism to "notify" your monitor process. You will have to be able to "trace back" from a "close" message back to a structure containing the name. You need to capture/save the name at _IO_OPEN. This is complicated by the fact that you are interested in "removable" filesystems... Dennis Tue, 21 Jun 2011 13:11:29 GMT http://community.qnx.com/sf/go/post86743 Dennis Kellly 2011-06-21T13:11:29Z http://community.qnx.com/sf/go/post86737 Hello All, I have a requirement to get notified(i do not know how) if a file is created inside say /dev/umass/xxx This is required for my app to spawn other drivers. Bascically i could use a loop and see if there were any new entry, but this solution does not look good and will consume more CPU. Can someone suggest a better method to monitor a directory path for dynamic file creation/removal? Eg: On file creation of /dev/umass/usb01100 & removal of /dev/umass/usb01100? Thanks in advance for your help. Regards, Lavin Tue, 21 Jun 2011 11:28:51 GMT http://community.qnx.com/sf/go/post86737 Lavin Pottekkat 2011-06-21T11:28:51Z http://community.qnx.com/sf/go/post85317 Well, if it helps any, I wrote a little q&d program to erase the CF, hoping it might fix the problem. It didn't have any effect, so I never turned it into a "nice" program, but you may find it helpful. This program just blindly sends erase commands until it gets an error. Your MUST NOT have devb-eide running at the same time as this program because it just writes the controller registers without any regard for other software trying to use the device. lew Fri, 29 Apr 2011 13:47:50 GMT http://community.qnx.com/sf/go/post85317 Lewis Donzis 2011-04-29T13:47:50Z http://community.qnx.com/sf/go/post85316 Hello, We have used Advantech Single Board Computers (SBCs) with Transcend 512MB industrial CFs. Those CFs started to be slow, develop bad blocks and some CFs froze after several days, they were undetectable in BIOS nor in card reader. But it happened only in specific type of SBC (probably different chipset and timing of ATA communication). We have been unable to find the reason, so we switched to other brand of CF for a given type of SBC. We stress tested these CFs in other SBC and they worked fine. Definitely not the problem of writing too much to the CF. PKY Fri, 29 Apr 2011 13:41:58 GMT http://community.qnx.com/sf/go/post85316 Pavol Kycina 2011-04-29T13:41:58Z http://community.qnx.com/sf/go/post85315 > Hello, > > would you be willing to share your test program? We have had issues with > Transcend and it's stability lately too. > > Regards, PKY Sure, no problem, here it is. On QNX, it was originally simpler with readblock() and writeblock(), but those functions didn't exist on Linux so we changed to using lseek() instead. Compile it with: cc -O3 -Wall cftest -ocftest Run it like this: ./cftest /dev/hd0 (or whichever device you want to test) It's non-destructive because it reads every block before writing it back. So..... what problems have you been having with Transcend? lew Fri, 29 Apr 2011 12:15:47 GMT http://community.qnx.com/sf/go/post85315 Lewis Donzis 2011-04-29T12:15:47Z http://community.qnx.com/sf/go/post85313 Hello, would you be willing to share your test program? We have had issues with Transcend and it's stability lately too. Regards, PKY > Update..... we took the slog info showing all of the commands that were issued > to the drive and wrote a little program to reply them, and it reproduces the > problem, completely independent from the qnx6 fs. So it has nothing to do > with the filesystem, but simple the pattern of writes that was done to the > flash. > > We then ported the test program to Linux and the problem occurs equally well. > > So bottom line, QNX is not at fault and we will pursue this with Transcend. > > Thank, > > lew Fri, 29 Apr 2011 09:04:45 GMT http://community.qnx.com/sf/go/post85313 Pavol Kycina 2011-04-29T09:04:45Z http://community.qnx.com/sf/go/post85310 Update..... we took the slog info showing all of the commands that were issued to the drive and wrote a little program to reply them, and it reproduces the problem, completely independent from the qnx6 fs. So it has nothing to do with the filesystem, but simple the pattern of writes that was done to the flash. We then ported the test program to Linux and the problem occurs equally well. So bottom line, QNX is not at fault and we will pursue this with Transcend. Thank, lew Thu, 28 Apr 2011 23:56:47 GMT http://community.qnx.com/sf/go/post85310 Lewis Donzis 2011-04-28T23:56:47Z http://community.qnx.com/sf/go/post85279 > We had similar issue with Transcend IDE flash drive (4G). Our solution was to > give up on this brand all together. Not that there bad but Transcend and QNX > don't seem to be compatible for some reason. > > At the time I didn't feel like paying big money to have this issue fix (custom > engineering). Plus from experience, through foundry, the feedback from QNX > is on the low side. I hear ya. We've been using Transcend for many years because, in our experience, their quality has been good, and they were the first out with really high-performance CF that supported DMA. That said, I would think that QNX would be interested in knowing why a standard, off the shelf CFA and ATA compliant device is not working properly. As you say, there appears to be some compatibility problem. Unfortunately, we have a large number of these already deployed in the field so switching to another brand is not so simple. We discovered the problem while testing a field upgrade image that reformats the filesystem as qnx6, but in this case, the box had to be returned to us after the flash died during that process. Yuck. Thanks, lew Wed, 27 Apr 2011 21:50:51 GMT http://community.qnx.com/sf/go/post85279 Lewis Donzis 2011-04-27T21:50:51Z http://community.qnx.com/sf/go/post85278 We had similar issue with Transcend IDE flash drive (4G). Our solution was to give up on this brand all together. Not that there bad but Transcend and QNX don't seem to be compatible for some reason. At the time I didn't feel like paying big money to have this issue fix (custom engineering). Plus from experience, through foundry, the feedback from QNX is on the low side. > We're using a Transcend Compact Flash, model TS2GCF266, which is 2G, 266X SLC. > The device does support the FLUSH CACHE command, and it works fine with sync > =mandatory. > > However, if I create a qnx6 fs on the device and then write several megabytes > worth of files, it gets a low-level error and the device seems to go into some > sort of write-protect mode where we have to cycle the power to clear it. > > What's odd is that we can do the exact same thing with qnx4 fs, and we can > write every sector on the device with dd. In fact, I created a qnx6fs on > another similar CF, and dd'ed the entire image to the "bad" flash without any > problem. The resulting CF boots up just fine, but any attempt to write a > large file to it produces errors in the slog and the device stops allowing > writes. > > I've tried everything I can think of, including sync=none, turning off DMA, > etc., and it makes no difference. "Something" that qnx6 fs is doing is > causing this flash device to give an error. > > I've reproduced in in various different machines, with two different CF > modules, HOWEVER, it doesn't happen with every module. I have a third CF of > the exact same make & model, and it does not exhibit the problem. > > I loaded "devb-eide eide verbose=5,master=verbose=5 cam verbose=5" and have > the slog output of the resulting error, if anyone wants to look at it. It > doesn't seem to have a lot of info, other than that it was doing a write of > 64K bytes and then the next thing is a "reset completed after ~300ms". > > If it was just a single device, I would dismiss it as bad, but two different > ones? > > Thanks, > lew Wed, 27 Apr 2011 21:15:06 GMT http://community.qnx.com/sf/go/post85278 Mario Charest 2011-04-27T21:15:06Z http://community.qnx.com/sf/go/post85276 We're using a Transcend Compact Flash, model TS2GCF266, which is 2G, 266X SLC. The device does support the FLUSH CACHE command, and it works fine with sync=mandatory. However, if I create a qnx6 fs on the device and then write several megabytes worth of files, it gets a low-level error and the device seems to go into some sort of write-protect mode where we have to cycle the power to clear it. What's odd is that we can do the exact same thing with qnx4 fs, and we can write every sector on the device with dd. In fact, I created a qnx6fs on another similar CF, and dd'ed the entire image to the "bad" flash without any problem. The resulting CF boots up just fine, but any attempt to write a large file to it produces errors in the slog and the device stops allowing writes. I've tried everything I can think of, including sync=none, turning off DMA, etc., and it makes no difference. "Something" that qnx6 fs is doing is causing this flash device to give an error. I've reproduced in in various different machines, with two different CF modules, HOWEVER, it doesn't happen with every module. I have a third CF of the exact same make & model, and it does not exhibit the problem. I loaded "devb-eide eide verbose=5,master=verbose=5 cam verbose=5" and have the slog output of the resulting error, if anyone wants to look at it. It doesn't seem to have a lot of info, other than that it was doing a write of 64K bytes and then the next thing is a "reset completed after ~300ms". If it was just a single device, I would dismiss it as bad, but two different ones? Thanks, lew Wed, 27 Apr 2011 19:55:01 GMT http://community.qnx.com/sf/go/post85276 Lewis Donzis 2011-04-27T19:55:01Z http://community.qnx.com/sf/go/post85146 Hi all, I need an official statement. YES or NO would be enough. Regards Michael Wed, 20 Apr 2011 07:47:00 GMT http://community.qnx.com/sf/go/post85146 Michael Tasche 2011-04-20T07:47:00Z http://community.qnx.com/sf/go/post85145 Hi Denniis, Thanks for the tips. I'll give it a go. Cheers. > David- > > The requirement for qdb is for an underlying "posix" filesystem. It won't > work on a simple link to /dev/shmem - so you are right looking for tmpfs. > Apparently, tmpfs satisfies the posix requirement, but more efficiently than a > full-blown ram filesystem. > > Short of having tmpfs, you can create a qnx4 filesystem in ram - more overhead > but should work fine! > > Create 4M ramdisk - it will show up as /dev/hd1t77 or something similar... > > # devb-ram ram capacity=8192 & > > Then format and mount... > > # dinit -h /dev/hd1t77 > # mount /dev/hd1t77 /ram > > Denniis Wed, 20 Apr 2011 07:40:51 GMT http://community.qnx.com/sf/go/post85145 David McMinn 2011-04-20T07:40:51Z http://community.qnx.com/sf/go/post85111 David- The requirement for qdb is for an underlying "posix" filesystem. It won't work on a simple link to /dev/shmem - so you are right looking for tmpfs. Apparently, tmpfs satisfies the posix requirement, but more efficiently than a full-blown ram filesystem. Short of having tmpfs, you can create a qnx4 filesystem in ram - more overhead but should work fine! Create 4M ramdisk - it will show up as /dev/hd1t77 or something similar... # devb-ram ram capacity=8192 & Then format and mount... # dinit -h /dev/hd1t77 # mount /dev/hd1t77 /ram Denniis Tue, 19 Apr 2011 12:52:34 GMT http://community.qnx.com/sf/go/post85111 Dennis Kellly 2011-04-19T12:52:34Z http://community.qnx.com/sf/go/post85107 Hi Andy, Thanks for your reply. I should probably mention the setup I'm using: Commercial QNX 6.5.0 Windows hosted for x86 target. Standard Neutrino RTOS, nothing else (i.e. I don't have Aviage) I can't seem to find io-fs-media on my system either, nor any docs about it, probably because I don't have Aviage. However, io-fs-media is mentioned in the multimedia document overview (http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=/com.qnx.doc.neutrino_sys_arch/mme.html), but the link to the docs for io-fs-media (http://www.qnx.com/developers/docs/6.5.0/topic/com.qnx.doc.mme_en_mme_utils_ref/io-fs.html) seems to go nowhere: Is there any other information about it, even just to confirm that it only comes with Aviage? If that's the case am I back to using etfs? Cheers. > Hi David, > > I believe typically io-fs-media is used for the RAM disk: > > e.g. > # io-fs-media -dtmp > > Cheers, > Andy > > > -----Original Message----- > From: David McMinn [mailto:community-noreply@qnx.com] > Sent: Monday, April 18, 2011 6:44 AM > To: general-filesystems > Subject: tmpfs > > Hi, > > I am currently looking for information on using tmpfs under QNX. I am > using qdb and the documentation for it mentions being able to use tmpfs > as a RAM based temporary storage. I have also seen other mentions of > people using tmpfs on these forums. > > However, I can't seem to find any further reference to tmpfs in the > documentation, or on my development system. Is it something that I'd > need to port from Linux? Or am I better using ETFS in RAM? I thought > having a transaction based FS would be overkill. > > Cheers. > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post85078 Tue, 19 Apr 2011 08:01:04 GMT http://community.qnx.com/sf/go/post85107 David McMinn 2011-04-19T08:01:04Z http://community.qnx.com/sf/go/post85095 Hi David, I believe typically io-fs-media is used for the RAM disk: e.g. # io-fs-media -dtmp Cheers, Andy -----Original Message----- From: David McMinn [mailto:community-noreply@qnx.com] Sent: Monday, April 18, 2011 6:44 AM To: general-filesystems Subject: tmpfs Hi, I am currently looking for information on using tmpfs under QNX. I am using qdb and the documentation for it mentions being able to use tmpfs as a RAM based temporary storage. I have also seen other mentions of people using tmpfs on these forums. However, I can't seem to find any further reference to tmpfs in the documentation, or on my development system. Is it something that I'd need to port from Linux? Or am I better using ETFS in RAM? I thought having a transaction based FS would be overkill. Cheers. _______________________________________________ General http://community.qnx.com/sf/go/post85078 Mon, 18 Apr 2011 16:36:18 GMT http://community.qnx.com/sf/go/post85095 Andrew Sherk 2011-04-18T16:36:18Z http://community.qnx.com/sf/go/post85078 Hi, I am currently looking for information on using tmpfs under QNX. I am using qdb and the documentation for it mentions being able to use tmpfs as a RAM based temporary storage. I have also seen other mentions of people using tmpfs on these forums. However, I can't seem to find any further reference to tmpfs in the documentation, or on my development system. Is it something that I'd need to port from Linux? Or am I better using ETFS in RAM? I thought having a transaction based FS would be overkill. Cheers. Mon, 18 Apr 2011 10:43:41 GMT http://community.qnx.com/sf/go/post85078 David McMinn 2011-04-18T10:43:41Z http://community.qnx.com/sf/go/post85019 We have an ancient P.C. which seems to be running QNX 2, I have a problem of how to get to the OS and do backups but in the mean time I have floppies created by someone else that are in QNX 2 format, is there a way I can copy these discs from a Windows P.C. so that I have a backup of them? Fri, 15 Apr 2011 07:04:36 GMT http://community.qnx.com/sf/go/post85019 Jonathan Leckie 2011-04-15T07:04:36Z http://community.qnx.com/sf/go/post84921 Hello David, what happens, if power goes away? Is the QNX6 filesystem (stored in the container file on ETFS) consistent after power loss? Michael > Michael, > > Devb-loopback uses a standard file descriptor to access the underlying > image. Because of this, nothing is different from ETFS, so the normal > ETFS power reliability rules apply. You might want to allow a bit more > time when flushing writes, since you first have to sync the qnx6 > filesystem, and THEN sync the ETFS filesystem, so any safe shutdown > should be sync'd twice. Otherwise, you'll be safe. > > David > > > -----Original Message----- > > From: Michael Tasche [mailto:community-noreply@qnx.com] > > Sent: April-12-11 5:50 AM > > To: general-filesystems > > Subject: QNX6 over ETFS powersafe ? > > > > Hi all, > > > > we have still problems with the etfs filesystem on big NAND-flashes > in > > projects with heavy filesystem use. > > e.g. : Crashing of resource manager, randomly poor performance, long > > mount times. > > > > We have got an experimental version of libetfs.a from the support > team, > > which solved some of the hardest problems, like total data-loss. > > We still have an active ticket, waiting for the next fixes. > > > > At the Moment I test a configuration with only one file in the etfs > > Filesystem > > This file contains a qnx6 filesystem, mounted over devb-loopback. > This > > configuration seems to work well without any etfs problems or limits. > > > > But is this configuration still powersafe? > > > > Regards > > Michael > > > > > > > > > > _______________________________________________ > > > > General > > http://community.qnx.com/sf/go/post84889 Wed, 13 Apr 2011 06:42:28 GMT http://community.qnx.com/sf/go/post84921 Michael Tasche 2011-04-13T06:42:28Z http://community.qnx.com/sf/go/post84898 Michael, Devb-loopback uses a standard file descriptor to access the underlying image. Because of this, nothing is different from ETFS, so the normal ETFS power reliability rules apply. You might want to allow a bit more time when flushing writes, since you first have to sync the qnx6 filesystem, and THEN sync the ETFS filesystem, so any safe shutdown should be sync'd twice. Otherwise, you'll be safe. David > -----Original Message----- > From: Michael Tasche [mailto:community-noreply@qnx.com] > Sent: April-12-11 5:50 AM > To: general-filesystems > Subject: QNX6 over ETFS powersafe ? > > Hi all, > > we have still problems with the etfs filesystem on big NAND-flashes in > projects with heavy filesystem use. > e.g. : Crashing of resource manager, randomly poor performance, long > mount times. > > We have got an experimental version of libetfs.a from the support team, > which solved some of the hardest problems, like total data-loss. > We still have an active ticket, waiting for the next fixes. > > At the Moment I test a configuration with only one file in the etfs > Filesystem > This file contains a qnx6 filesystem, mounted over devb-loopback. This > configuration seems to work well without any etfs problems or limits. > > But is this configuration still powersafe? > > Regards > Michael > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post84889 Tue, 12 Apr 2011 13:46:27 GMT http://community.qnx.com/sf/go/post84898 David Sarrazin 2011-04-12T13:46:27Z http://community.qnx.com/sf/go/post84889 Hi all, we have still problems with the etfs filesystem on big NAND-flashes in projects with heavy filesystem use. e.g. : Crashing of resource manager, randomly poor performance, long mount times. We have got an experimental version of libetfs.a from the support team, which solved some of the hardest problems, like total data-loss. We still have an active ticket, waiting for the next fixes. At the Moment I test a configuration with only one file in the etfs Filesystem This file contains a qnx6 filesystem, mounted over devb-loopback. This configuration seems to work well without any etfs problems or limits. But is this configuration still powersafe? Regards Michael Tue, 12 Apr 2011 09:49:43 GMT http://community.qnx.com/sf/go/post84889 Michael Tasche 2011-04-12T09:49:43Z http://community.qnx.com/sf/go/post84011 Usage of DCMD_CAM_DEVICE_TEMPERATURE always returns ENOTTY. Is it because it's not supprted at all? Tue, 15 Mar 2011 19:33:06 GMT http://community.qnx.com/sf/go/post84011 Mario Charest 2011-03-15T19:33:06Z http://community.qnx.com/sf/go/post83887 The post contains invalid characters .Please click uhe above post link to view the content. Thu, 10 Mar 2011 09:07:27 GMT http://community.qnx.com/sf/go/post83887 Christophe Hannoyer 2011-03-10T09:07:27Z http://community.qnx.com/sf/go/post83886 Hi Dennis, Yeah, good catch, I totally missed that 0 Total Sectors. > "After deleting partitions > # fdisk /dev/hd0 info > > Physical disk characteristics: (/dev/hd0) > ... > Total Sectors :>>>> 0<<<< > > Warning: total sectors field does not agree with > cylinders*sectors/track*heads!! (>>>>0<<<< vs 15661056)" > > ------------------------------------------------------ > As long as the system cannot determine total sectors (15662304) from the > device, not sure how it could work! Have you tried rebooting AFTER deleting > all partitions? In theory, that should update total sectors. Anyway this problem got solved when I did mount -e /dev/hd0 after deleting partitions as Christophe mentioned. > > I will venture that the CF flash units that work have 63 spt (not 32) - as > well as 255 heads (not 64). > I am not sure on this as I have other 1 GB CF which works perfectly fine and has spt and head similar to Kingston's 8GB CF. Physical disk characteristics: (/dev/hd0) Disk type : Direct Access (0) Cylinders : 977 Heads : 64 Sectors/Track : 32 Total Sectors : 2001888 Warning: total sectors field does not agree with cylinders*sectors/track*heads!! (2001888 vs 2000896) Best Regards, Apurva Thu, 10 Mar 2011 07:33:57 GMT http://community.qnx.com/sf/go/post83886 Apurva P 2011-03-10T07:33:57Z http://community.qnx.com/sf/go/post83885 The post contains invalid characters .Please click uhe above post link to view the content. Thu, 10 Mar 2011 07:25:06 GMT http://community.qnx.com/sf/go/post83885 Apurva P 2011-03-10T07:25:06Z http://community.qnx.com/sf/go/post83861 "After deleting partitions # fdisk /dev/hd0 info Physical disk characteristics: (/dev/hd0) ... Total Sectors :>>>> 0<<<< Warning: total sectors field does not agree with cylinders*sectors/track*heads!! (>>>>0<<<< vs 15661056)" ------------------------------------------------------ As long as the system cannot determine total sectors (15662304) from the device, not sure how it could work! Have you tried rebooting AFTER deleting all partitions? In theory, that should update total sectors. I will venture that the CF flash units that work have 63 spt (not 32) - as well as 255 heads (not 64). Dennis Wed, 09 Mar 2011 13:39:59 GMT http://community.qnx.com/sf/go/post83861 Dennis Kellly 2011-03-09T13:39:59Z http://community.qnx.com/sf/go/post83859 When the boot of CD has completed, the CD filesystem is not mounted on /fs/cd0 in the traditional sense. (Run 'mount' from a shell.) Rather. the FILE '/fs/cd0/boot/fs/qnxbase.qfs' (an archive) has been mounted as '/' of the running system. Removing the media will break this necessary mount and the running system will not be able to function as intended. No removal/insertion logic can mount new media due to the archive mount at /. Dennis Wed, 09 Mar 2011 13:18:32 GMT http://community.qnx.com/sf/go/post83859 Dennis Kellly 2011-03-09T13:18:32Z http://community.qnx.com/sf/go/post83858 Did you tried to run "mount -e"? # fdisk /dev/hd0 info # fdisk /dev/hd0 delete -a # mount -e /dev/hd0 # fdisk /dev/hd0 info Christophe > From: Apurva P [mailto:community-noreply@qnx.com] > Sent: Tuesday, March 08, 2011 7:13 PM > To: general-filesystems > Subject: CompactFlash Partitioning with fdisk > > Hi, > > I am having problem partitioning Kingston 8GB (CF/8GB) CompactFlash using > fdisk. > > Please let me describe what I want to do is to delete previous partitions on CF > and create two new partition: one raw and second qnx6. Therefore my > procedure should be, > > //Delete Previous Partitions > #fdisk /dev/hd0 delete –a > > //Create around 16 MB first raw partition. > #fdisk /dev/hd0 add -b -c 0,15 -t 180 > > //Create second qnx6fs partition. > #fdisk /dev/hd0 add -t 179 > > > But problem is that when I issue first command to delete previous partitions > something wrong happens and two known partitions appears when I do fdisk > /dev/hd0 info. > > Here is my steps and fdisk output > > // Previous condition > # fdisk /dev/hd0 info > > /dev/hd0 info Physical disk characteristics: (/dev/hd0) > Disk type : Direct Access (0) > Cylinders : 7647 > Heads : 64 > Sectors/Track : 32 > Total Sectors : 15662304 > > Warning: total sectors field does not agree with > cylinders*sectors/track*heads!! (15662304 vs 15661056) > > Partition table information: > 0: (180) beg(h=1,s=1,c=0) end(h=63,s=32,c=15) off=32, size=32736 > 1: (179) beg(h=0,s=1,c=16) end(h=63,s=224,c=208) off=32768, > size=1968128 > 2: (0) beg(h=0,s=0,c=0) end(h=0,s=0,c=0) off=0, size=0 > 3: (0) beg(h=0,s=0,c=0) end(h=0,s=0,c=0) off=0, size=0 signature1=0x55, > signature2=0xAA > > > # fdisk /dev/hd0 delete -a > > //After deleting partitions > # fdisk /dev/hd0 info > > Physical disk characteristics: (/dev/hd0) > Disk type : Direct Access (0) > Cylinders : 7647 > Heads : 64 > Sectors/Track : 32 > Total Sectors : 0 > > Warning: total sectors field does not agree with > cylinders*sectors/track*heads!! (0 vs 15661056) > > Partition table information: > 0: (0) beg(h=0,s=0,c=0) end(h=0,s=72,c=4) off=0, size=88604672 > 1: (0) beg(h=16,s=0,c=0) end(h=0,s=0,c=0) off=0, size=1769734144 > 2: (192) beg(h=179,s=72,c=5) end(h=0,s=0,c=0) off=256, size=18274 > 3: (144) beg(h=0,s=72,c=5) end(h=16,s=72,c=4) off=71834633, > size=71867395 signature1=0x01, signature2=0x28 > > > Please can anyone tell me where things are going wrong? This problem only > exist with 8 GB Kingston CompactFlash. I have tested other 1 and 2 GB CFs and > everything's fine. > > I have also attached sloginfo. > > Thank you very much, > Apurva > > > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post83831 Wed, 09 Mar 2011 13:13:04 GMT http://community.qnx.com/sf/go/post83858 Christophe Hannoyer 2011-03-09T13:13:04Z http://community.qnx.com/sf/go/post83850 Hi QNX expert, here is my steps to do my testing, 1. insert a CD ,and run command "ls /fs/cd0", get some output 2.remove the CD and insert another CD 3."ls /fs/cd0" , but the output is the first CD's contents. I also tested these steps on QNX650,the contents will update in QNX650 Plese help. Wed, 09 Mar 2011 08:59:19 GMT http://community.qnx.com/sf/go/post83850 shen xifeng 2011-03-09T08:59:19Z http://community.qnx.com/sf/go/post83831 Hi, I am having problem partitioning Kingston 8GB (CF/8GB) CompactFlash using fdisk. Please let me describe what I want to do is to delete previous partitions on CF and create two new partition: one raw and second qnx6. Therefore my procedure should be, //Delete Previous Partitions #fdisk /dev/hd0 delete –a //Create around 16 MB first raw partition. #fdisk /dev/hd0 add -b -c 0,15 -t 180 //Create second qnx6fs partition. #fdisk /dev/hd0 add -t 179 But problem is that when I issue first command to delete previous partitions something wrong happens and two known partitions appears when I do fdisk /dev/hd0 info. Here is my steps and fdisk output // Previous condition # fdisk /dev/hd0 info /dev/hd0 info Physical disk characteristics: (/dev/hd0) Disk type : Direct Access (0) Cylinders : 7647 Heads : 64 Sectors/Track : 32 Total Sectors : 15662304 Warning: total sectors field does not agree with cylinders*sectors/track*heads!! (15662304 vs 15661056) Partition table information: 0: (180) beg(h=1,s=1,c=0) end(h=63,s=32,c=15) off=32, size=32736 1: (179) beg(h=0,s=1,c=16) end(h=63,s=224,c=208) off=32768, size=1968128 2: (0) beg(h=0,s=0,c=0) end(h=0,s=0,c=0) off=0, size=0 3: (0) beg(h=0,s=0,c=0) end(h=0,s=0,c=0) off=0, size=0 signature1=0x55, signature2=0xAA # fdisk /dev/hd0 delete -a //After deleting partitions # fdisk /dev/hd0 info Physical disk characteristics: (/dev/hd0) Disk type : Direct Access (0) Cylinders : 7647 Heads : 64 Sectors/Track : 32 Total Sectors : 0 Warning: total sectors field does not agree with cylinders*sectors/track*heads!! (0 vs 15661056) Partition table information: 0: (0) beg(h=0,s=0,c=0) end(h=0,s=72,c=4) off=0, size=88604672 1: (0) beg(h=16,s=0,c=0) end(h=0,s=0,c=0) off=0, size=1769734144 2: (192) beg(h=179,s=72,c=5) end(h=0,s=0,c=0) off=256, size=18274 3: (144) beg(h=0,s=72,c=5) end(h=16,s=72,c=4) off=71834633, size=71867395 signature1=0x01, signature2=0x28 Please can anyone tell me where things are going wrong? This problem only exist with 8 GB Kingston CompactFlash. I have tested other 1 and 2 GB CFs and everything's fine. I have also attached sloginfo. Thank you very much, Apurva Tue, 08 Mar 2011 18:12:58 GMT http://community.qnx.com/sf/go/post83831 Apurva P 2011-03-08T18:12:58Z http://community.qnx.com/sf/go/post83759 Hi all, I was wondering if somebody could point me to right direction. As per the QNX documentation, QNX can understand MBR/EBR partition formats and can parse the same. Our current solution has a number of partition entries in the MBR/EBR that we are somehow not able to see once QNX is running. It seems that QNX is somehow corrupting the MBR/EBR programmed in the device. To avoid this we would like to allocate a QNX partition in the MBR/EBR partition table such that QNX can identify that is the only partition that is accessible to them instead of taking over the complete device. I have the following questions: (1) When there is a valid MBR/EBR, in what scenario would QNX completely erase the device? (2) How can I get QNX to recognize our MBR/EBR partition table programmed in the device? (3) How can I get a single QNX partition in the MBR/EBR that QNX can use only that partition for their file system and leave the rest of the region intact? (4) What type would this need to be for QNX to identify its partition. The MBR partition types indicates it should be type=77. (5) We already use the type 77 for some other non-QNX partition. Can that cause an issue? I would highly appreciate any information on this. Thanks. Asheesh. Fri, 04 Mar 2011 20:47:08 GMT http://community.qnx.com/sf/go/post83759 Asheesh Kumar 2011-03-04T20:47:08Z http://community.qnx.com/sf/go/post83702 I currently have a makefile that creates partitions on a CF card and uses unmount and mount on the card surrounding the partition creation. I would like to use mcd so that the makefile won't need root privileges. devb-umass is started with: devb-umass cam pnp & mcd is started with: mcd -I .insert -E .eject /etc/mcd.conf USB attached CF card shows up as /dev/hd1 I have the following lines in mcd.conf: [/dev/hd[1-9]*] Callout = PATH_MEDIA_PROCMGR Argument = /proc/mount Priority = 11,10 Start Rule = MOUNT Stop Rule = UNMOUNT [MOUNT] Callout = MOUNT_FSYS Argument = /etc/mcd.mnt [UNMOUNT] Callout = UNMOUNT_FSYS And the following lines in mcd.mnt /dev/hd[1-9]* / enum /dev/hd[1-9]*t77 /fs/hd%#t77 qnx4 normv /dev/hd[1-9]*t78 /fs/hd%#t78 qnx4 normv /dev/hd[1-9]*t79 /fs/hd%#t79 qnx4 normv when the USB CF card reader is plugged in everything mounts as expected, when unplugged everything umounts as expected. however with the makefile I would like to leave the reader plugged in, trigger an eject if the partitions are mounted, rewrite the partitions and then trigger an insert and have the partitions mounted. according to this page: http://www.qnx.com/developers/docs/6.4.1/neutrino/utilities/m/mcd.html I should be able to write the path of the device to /dev/mcd/.insert and have it trigger an insert action or write the path to /dev/mcd/.eject to trigger an eject. I've tried using: echo "/dev/hd2t77" >> /dev/mcd/.eject but it remains mounted likewise echo "/dev/hd2t77" >> /dev/mcd/.insert doesn't seem to trigget an insert event I've searched around but couldn't find much info regarding the use of .insert and .eject. Any help would be greatly appreciated. Thanks, Michael Wed, 02 Mar 2011 22:35:18 GMT http://community.qnx.com/sf/go/post83702 Michael Stinaff 2011-03-02T22:35:18Z http://community.qnx.com/sf/go/post83200 Hi, A customer is considering using a new Micron NAND part (MT29F1G08ABADAWP) which uses 4 bit ECC. All of our docs I can find only refer to 1 bit ECC. Could we support the above part including 4 bit ECC as custom engineering? If so, how big a task would it be? Thanks, Garry Wed, 16 Feb 2011 11:30:33 GMT http://community.qnx.com/sf/go/post83200 Garry Bleasdale 2011-02-16T11:30:33Z http://community.qnx.com/sf/go/post82634 -----Original Message----- From: Mario Charest [mailto:community-noreply@qnx.com] Sent: January-24-11 7:26 PM To: general-filesystems Subject: Re: RE: qnx6f max file number > > > > -----Message d'origine----- > > De : David Sarrazin [mailto:community-noreply@qnx.com] > > Envoyé : 20 septembre 2010 09:55 > > À : general-filesystems > > Objet : RE: qnx6f max file number > > > > Each inode requires 128 bytes, so 100M inodes is 12.8GB, plus the indirect > > blocks. Finding a free inode in a mostly-full system would be time > expensive > > at that scale. What you are saying is that you expect your 2TB drive to be > > filled up with 10KByte average-sized files. Having said that, I know that > the > > test group here has a 2TB server set up with 10M inodes. > > > That would be 20K files ;-) I exaggerated that number a bit to get a good > idea. Files will be 400K so 5 millions would be closer to what we need. > > Can you define 'time expensive'? The hardware driver will operate almost 90% > full, with around 100 files new files written and the 100 oldest files deleted > . Given mkqnx6fs -i12000000 on a 2Terabyte disk filled at 8% is it possible that a write of 20 files (20Meg) will cause the filesystem to freeze for 10-20Sec ? I would expect no. If you've used up most of the inodes, and have just a few free holes spread about in the inodes file, then finding a free inode will incur a search through the file (a hint to where to start searching is stored). If this was a new filesystem, the inodes file will be almost entirely free, and finding new entries will be very fast. Does a KEV show what the "fsys_resmgr" threads in devb are doing? David _______________________________________________ General http://community.qnx.com/sf/go/post82603 Tue, 25 Jan 2011 16:20:17 GMT http://community.qnx.com/sf/go/post82634 David Sarrazin 2011-01-25T16:20:17Z http://community.qnx.com/sf/go/post82603 > > > > -----Message d'origine----- > > De : David Sarrazin [mailto:community-noreply@qnx.com] > > Envoyé : 20 septembre 2010 09:55 > > À : general-filesystems > > Objet : RE: qnx6f max file number > > > > Each inode requires 128 bytes, so 100M inodes is 12.8GB, plus the indirect > > blocks. Finding a free inode in a mostly-full system would be time > expensive > > at that scale. What you are saying is that you expect your 2TB drive to be > > filled up with 10KByte average-sized files. Having said that, I know that > the > > test group here has a 2TB server set up with 10M inodes. > > > That would be 20K files ;-) I exaggerated that number a bit to get a good > idea. Files will be 400K so 5 millions would be closer to what we need. > > Can you define 'time expensive'? The hardware driver will operate almost 90% > full, with around 100 files new files written and the 100 oldest files deleted > . Given mkqnx6fs -i12000000 on a 2Terabyte disk filled at 8% is it possible that a write of 20 files (20Meg) will cause the filesystem to freeze for 10-20Sec ? > Tue, 25 Jan 2011 00:26:12 GMT http://community.qnx.com/sf/go/post82603 Mario Charest 2011-01-25T00:26:12Z http://community.qnx.com/sf/go/post82453 Do QNX Support TRIM command for SSD disks? Tue, 18 Jan 2011 16:57:21 GMT http://community.qnx.com/sf/go/post82453 Marcus Bortel 2011-01-18T16:57:21Z http://community.qnx.com/sf/go/post82079 When I read the bsp code , I saw cam_configure() in the devb directory. This function is defined in libcam.so. Where I can get its doc or description? I just could not find any infomation in the user guide. BR Jerry Thu, 13 Jan 2011 06:09:26 GMT http://community.qnx.com/sf/go/post82079 Jerry Van 2011-01-13T06:09:26Z http://community.qnx.com/sf/go/post82078 I tested the file r/w performance on sd card using imx53 bsp, and the result is 0.8Mb/s(write) and 10Mb/s(read). The writting data rate is much lower than the result on eCos(A RTOS) while reading rate is a lilltle bit higher. Can anybody explain that? Or any suggestion to impove the writting performance. Thu, 13 Jan 2011 05:58:09 GMT http://community.qnx.com/sf/go/post82078 Jerry Van 2011-01-13T05:58:09Z http://community.qnx.com/sf/go/post80830 Hi, We are currently using 2 AM3517EVM boards for a student project prototype. I was able to create my ETFS filesystem and after copying the files I needed using qconn and Momentics. I was not able to create a transaction log and use etfsctl to write it in the NAND. After I copied all the files manually I used etfsctl on the board to save the filesystem in a file with: etfsctl -d /dev/etfs2 -r am3517evm.etfs When I tried to restore the filesystem on the other board, I keep getting this error: error writing transactions to flash: No space left on device Error status on option 'w' : No space left on device The exact command I used is: etfsctl -d /dev/etfs2 -S -e -w am3517evm.etfs -c Both boards have the same IPL, IFS and the same Flash. If anyone has an idea what I'm doing wrong and can point me in the right direction I would appreciate. Thanks, Marc Sun, 02 Jan 2011 04:23:46 GMT http://community.qnx.com/sf/go/post80830 Marc-Andre Courtois 2011-01-02T04:23:46Z http://community.qnx.com/sf/go/post80503 In my system,i get SD card with two file system,one is FAT32 and another is QNX6.SD card is attach in file [/dev/hd1],After executed [mount -e /dev/hd1], i got [ hd1t14] and [hd1t179] in path [dev]. now i search in [dev] path to find some files that's name started with [hd1t],is there any better way to find it? I try send [DCMD_FSYS_MOUNTED_ON] use devctl function,but only can get [/dev/hd1] form [/dev/hd1t14]. Tue, 28 Dec 2010 05:06:56 GMT http://community.qnx.com/sf/go/post80503 mu chunyu 2010-12-28T05:06:56Z http://community.qnx.com/sf/go/post76493 Hi, We have a customer benchmarking our SD card / DOS filesystem performance using our Atmel 9G45 BSP. He is seeing write speeds of 0.7MB/sec and comparing this to his own RTOS + driver with speeds of 7MB/sec. Are the speeds he is seeing about what we would expect? Is there anything he could try to improve this? Thanks, Garry Tue, 30 Nov 2010 17:29:50 GMT http://community.qnx.com/sf/go/post76493 Garry Bleasdale 2010-11-30T17:29:50Z http://community.qnx.com/sf/go/post76376 The Filesystem classes stated that Nonblock-oriented filesystems designed explicitly for the characteristics of flash memory devices. For NOR devices, use the FFS3 filesystem; for NAND, use ETFS so does etfs work for nor flash? Is there a way to put debug code in the flash translation layer (FTL) which reside between filesystem and flash driver? Tue, 30 Nov 2010 00:19:44 GMT http://community.qnx.com/sf/go/post76376 handoko chendra 2010-11-30T00:19:44Z http://community.qnx.com/sf/go/post76246 Hello, who can share me a etfs builfile template? I compile the source file and get *.o files, but I don't have buildfile and don't know how to generate etfs file from mketfs. if I get the etfs file how can I combine the os image and ipl imange? Mon, 29 Nov 2010 09:52:02 GMT http://community.qnx.com/sf/go/post76246 guo wei 2010-11-29T09:52:02Z http://community.qnx.com/sf/go/post75425 Look at "etfs". That is the filesystem for direct (bus) connected flash. You will probably want to download a bsp (similar to your board) and "port" the etfs driver source which links to the etfs library (libetfs.a). The most important parameter is the "page size" (512, 2048, etc) - make sure you start with source matching your pagesize. Sat, 20 Nov 2010 13:40:03 GMT http://community.qnx.com/sf/go/post75425 Dennis Kellly 2010-11-20T13:40:03Z http://community.qnx.com/sf/go/post75406 I wonder how to port a flash filesystem into QNX filesystem. Should it be connected to the io_block.so? and how can I download the filesystem source code? Thank you Fri, 19 Nov 2010 22:44:16 GMT http://community.qnx.com/sf/go/post75406 handoko chendra 2010-11-19T22:44:16Z http://community.qnx.com/sf/go/post74527 After re-reading your original question, I don't think an extra .diskroot file is your problem (it isn't used until later). As I understand it, the primary boot loader should time-out and boot the default partition. What's the second partition for? Fri, 12 Nov 2010 20:39:48 GMT http://community.qnx.com/sf/go/post74527 Steve Reid 2010-11-12T20:39:48Z http://community.qnx.com/sf/go/post74523 > >> Remove de .diskboot file on the second disk/partition > > Where do I find this .diskboot file -- in which sub-directory -- I cannot > locate it anywhere. > > Did you perhaps mean .diskroot rather then .diskboot ??? > > I've very sorry to be so obtuse but I have very little experience with > filesystems > > Thanks in Advanced > > James Kelley Yes, it should be .diskroot. See the Controlling How Neutrino Starts chapter of the Neutrino User's Guide: http://www.qnx.com/developers/docs/6.5.0/topic/com.qnx.doc.neutrino_user_guide/starting.html Steve Reid (stever@qnx.com) Technical Editor QNX Software Systems Fri, 12 Nov 2010 20:32:00 GMT http://community.qnx.com/sf/go/post74523 Steve Reid 2010-11-12T20:32:00Z http://community.qnx.com/sf/go/post74522 Further Information If I run the df command, I get the following: /dev/hd0t179 8160920 5259310 2901610 65% / /dev/hd0t177 23085184 788762 22296422 4% /fs/hd0-qnx6-2/ /dev/hd0 31277056 31277056 0 100% I am assuming /dev/hd0t177 is the second partition but if I run ls -la on /fs/hd0-qnx6-2 I get the following drwxrwxr-x 3 root root 1024 Sep 30 18:16 . drwxrwxr-x 3 root root 1024 Sep 30 18:16 .. drwx------ 2 root root 1024 Sep 30 18:16 .boot I can find no files or other sub-directories in .boot Any other suggestions Fri, 12 Nov 2010 20:27:20 GMT http://community.qnx.com/sf/go/post74522 James Kelley 2010-11-12T20:27:20Z http://community.qnx.com/sf/go/post74519 >> Remove de .diskboot file on the second disk/partition Where do I find this .diskboot file -- in which sub-directory -- I cannot locate it anywhere. Did you perhaps mean .diskroot rather then .diskboot ??? I've very sorry to be so obtuse but I have very little experience with filesystems Thanks in Advanced James Kelley Fri, 12 Nov 2010 20:10:14 GMT http://community.qnx.com/sf/go/post74519 James Kelley 2010-11-12T20:10:14Z http://community.qnx.com/sf/go/post74234 > Mario, > > This is a known issue which has just recently been fixed in dcheck. If > your disk is <= 1TB, the 6.4.1 dcheck will still work for you. > It's a 2TB disk. > David > > > -----Original Message----- > > From: Mario Charest [mailto:community-noreply@qnx.com] > > Sent: November 10, 2010 10:53 AM > > To: general-filesystems > > Subject: dcheck problem > > > > I've tried it on three different machines and when I start dcheck it > > return right away with the following mesasge: > > > > Read check of /net/controller.gradexpert.buchanan/dev/hd0t179 without > > bad block marking, > > starting at block 1 for the remainder of the disk. > > Checking 2104452 512-byte blocks > > > > And that's it. Nothing in sloginfo. > > > > > > > > _______________________________________________ > > > > General > > http://community.qnx.com/sf/go/post74219 Wed, 10 Nov 2010 16:45:15 GMT http://community.qnx.com/sf/go/post74234 Mario Charest 2010-11-10T16:45:15Z http://community.qnx.com/sf/go/post74227 Mario, This is a known issue which has just recently been fixed in dcheck. If your disk is <= 1TB, the 6.4.1 dcheck will still work for you. David > -----Original Message----- > From: Mario Charest [mailto:community-noreply@qnx.com] > Sent: November 10, 2010 10:53 AM > To: general-filesystems > Subject: dcheck problem > > I've tried it on three different machines and when I start dcheck it > return right away with the following mesasge: > > Read check of /net/controller.gradexpert.buchanan/dev/hd0t179 without > bad block marking, > starting at block 1 for the remainder of the disk. > Checking 2104452 512-byte blocks > > And that's it. Nothing in sloginfo. > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post74219 Wed, 10 Nov 2010 16:25:50 GMT http://community.qnx.com/sf/go/post74227 David Sarrazin 2010-11-10T16:25:50Z http://community.qnx.com/sf/go/post74219 I've tried it on three different machines and when I start dcheck it return right away with the following mesasge: Read check of /net/controller.gradexpert.buchanan/dev/hd0t179 without bad block marking, starting at block 1 for the remainder of the disk. Checking 2104452 512-byte blocks And that's it. Nothing in sloginfo. Wed, 10 Nov 2010 15:52:34 GMT http://community.qnx.com/sf/go/post74219 Mario Charest 2010-11-10T15:52:34Z http://community.qnx.com/sf/go/post74145 Thanks for the reply David. There is no information in sloginfo. Heres the output from chkdosfs Filesystem is marked clean (use '-u' to force check) and then with the -u to force the check... Phase 1 - Read and compare FATs Phase 2 - Check cluster chains Phase 3 - Check directories Phase 4 - Check for lost files 2 kb used, 32735 kb free, 0 files, 2 directories Filesystem is clean. I'm beginning to think theres a minimum size for a FAT32 partition in QNX.(smaller than the one required by Linux) I created and formatted this partition in Linux, which can mount and r/w the partition just fine. But as I have read many times in these forums, QNX is not Linux. So I decided to let QNX format the partition using mkdosfs and QNX decided that it was much happier with this tiny partition as FAT16 Format complete: FAT16 (2048-byte clusters), 33183 kB available. That solves my problem since FAT32 was not a requirement for this project and I can now r/w the partition in Windoze and Linux. Thanks for taking a look. Jerry > We don't ship mount_dos, because it is not needed to mount the > filesystem. If chkdosfs /dev/hd0t11 returns with no errors, then I'm > surprised this doesn't mount. Is there any information in sloginfo? > > David > > > -----Original Message----- > > From: Jerry Reiner [mailto:community-noreply@qnx.com] > > Sent: November 9, 2010 2:33 PM > > To: general-filesystems > > Subject: Re: Mounting Fat32 results in Corrupted file system detected > > > > Thanks Dennis, I've tried that and I get the same error. > > > > increasing the verbosity of the mount command reveals the source of my > > problem (but not the solution) > > > > Parsed: mount from [/dev/hd0t11] mount on [/wtf] type [dos] > > exec: mount_dos /dev/hd0t11 /wtf > > Using internal mount (mount_dos not found) > > Type [dos] Flags 0x00000000 > > Device [/dev/hd0t11] Directory [/wtf] > > Options [NULL] > > > > So mount_dos is not in my bsp image. Unfortunately its also not > > included in my Neutrino development suite nor is it in any of the 2 > > vmware images I have tried running. So the million dollar question is > > how do I get mount_dos? > > > > > > > > > > > > _______________________________________________ > > > > General > > http://community.qnx.com/sf/go/post74129 Tue, 09 Nov 2010 20:26:19 GMT http://community.qnx.com/sf/go/post74145 Jerry Reiner 2010-11-09T20:26:19Z http://community.qnx.com/sf/go/post74134 We don't ship mount_dos, because it is not needed to mount the filesystem. If chkdosfs /dev/hd0t11 returns with no errors, then I'm surprised this doesn't mount. Is there any information in sloginfo? David > -----Original Message----- > From: Jerry Reiner [mailto:community-noreply@qnx.com] > Sent: November 9, 2010 2:33 PM > To: general-filesystems > Subject: Re: Mounting Fat32 results in Corrupted file system detected > > Thanks Dennis, I've tried that and I get the same error. > > increasing the verbosity of the mount command reveals the source of my > problem (but not the solution) > > Parsed: mount from [/dev/hd0t11] mount on [/wtf] type [dos] > exec: mount_dos /dev/hd0t11 /wtf > Using internal mount (mount_dos not found) > Type [dos] Flags 0x00000000 > Device [/dev/hd0t11] Directory [/wtf] > Options [NULL] > > So mount_dos is not in my bsp image. Unfortunately its also not > included in my Neutrino development suite nor is it in any of the 2 > vmware images I have tried running. So the million dollar question is > how do I get mount_dos? > > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post74129 Tue, 09 Nov 2010 19:45:47 GMT http://community.qnx.com/sf/go/post74134 David Sarrazin 2010-11-09T19:45:47Z http://community.qnx.com/sf/go/post74129 Thanks Dennis, I've tried that and I get the same error. increasing the verbosity of the mount command reveals the source of my problem (but not the solution) Parsed: mount from [/dev/hd0t11] mount on [/wtf] type [dos] exec: mount_dos /dev/hd0t11 /wtf Using internal mount (mount_dos not found) Type [dos] Flags 0x00000000 Device [/dev/hd0t11] Directory [/wtf] Options [NULL] So mount_dos is not in my bsp image. Unfortunately its also not included in my Neutrino development suite nor is it in any of the 2 vmware images I have tried running. So the million dollar question is how do I get mount_dos? Tue, 09 Nov 2010 19:32:57 GMT http://community.qnx.com/sf/go/post74129 Jerry Reiner 2010-11-09T19:32:57Z http://community.qnx.com/sf/go/post74079 >>># mount /dev/hd0t11 /someDir Try # mount -tdos /dev/hd0t11 /someDir Tue, 09 Nov 2010 17:36:14 GMT http://community.qnx.com/sf/go/post74079 Dennis Kellly 2010-11-09T17:36:14Z http://community.qnx.com/sf/go/post74077 I am booting QNX 6.4.1 from the second partition on a usb drive. The first partition is FAT32. The idea is to store the configuration files on the FAT32 partition so that they can be edited in the field by technicians on their Windoze laptops. The problem that I'm having is that when I run # mount /dev/hd0t11 /someDir no error but then # ls /someDir ls: Corrupted file system detected (/someDir) running chkfsdos returns no errors. I am running this off of a bsp that was created for me so I realize that I may be missing an executable or a dll or some other necessary item. I have looked for Fatfsys, Dosfsys, and mount_dos and have not been able to locate any of those items. I did add fs-dos.so Any help at all is greatly appreciated. Tue, 09 Nov 2010 17:33:47 GMT http://community.qnx.com/sf/go/post74077 Jerry Reiner 2010-11-09T17:33:47Z http://community.qnx.com/sf/go/post70249 Thanks. I was going by your original post - "I can plug in a USB stick and it shows up as /dev/hd1 and /dev/hd1t6" When I was trying mcd, I was booting a simple ifs from usbstick - so no remount of / to hd0 occured. Iin this case the usbstick is not mounted - even though you boot from it via the bios. I ended up writing code to find the mass storage device using "usb" binary, parsing values for vid, did, busno, devno and issuing a mount the boot device directly. Tue, 12 Oct 2010 13:33:01 GMT http://community.qnx.com/sf/go/post70249 Dennis Kellly 2010-10-12T13:33:01Z http://community.qnx.com/sf/go/post70241 OK people, here is the final part to getting mcd to work. I added the following to the boot script: mount /dev/hd0t77 / Apparently, mcd doesn't like the virtual file system the boot image creates. It wants a real file system to recognize removable devices. Michael, thanks for the devb-umass command options. I'll want to decompose them to figure out exactly what they mean but will likely use them because that's what everyone else does. Dennis, the peculiar name differences appears to be an artifact of the enum-devices program, which I am not using. With this configuration, the USB stick always shows up as /fs/usb0 even if it is present during booting. Tue, 12 Oct 2010 13:11:58 GMT http://community.qnx.com/sf/go/post70241 Robert Murrell 2010-10-12T13:11:58Z http://community.qnx.com/sf/go/post70221 > >>> I can plug in a USB stick and it shows up as /dev/hd1 and /dev/hd1t6. Well, I think you could miss "blk auto=none" . We have a working mcd configuration with followinh devb-umass options: "devb-umass cam pnp,quit,verbose blk cache=1m,vnode=384,auto=none,delwri=2:2,rmvto=none,noatime disk name=umass" -Michael Tue, 12 Oct 2010 10:15:36 GMT http://community.qnx.com/sf/go/post70221 Michael Tasche 2010-10-12T10:15:36Z http://community.qnx.com/sf/go/post70214 >>> I can plug in a USB stick and it shows up as /dev/hd1 and /dev/hd1t6. One thing that is going on here is that, when a usbstick is present AT BOOT, it shows up as above, say /dev/hd1. If instead, you boot WITHOUT the usbstick in place, and then insert it after boot, it will be /dev/umass0. In other words, "mcd" is not used if the usbstick is present when the system boots. It is only used LATER when the usb stack reports a new device has been detected. [I don't believe it should work two different ways, but it does...] So changing mcd.conf will never affect the device name - if usbstick is present at system boot. BTW - I gave up trying to get mcd to work from a minimal ifs. There must be some undocumented magic somewhere... Dennis Mon, 11 Oct 2010 21:10:26 GMT http://community.qnx.com/sf/go/post70214 Dennis Kellly 2010-10-11T21:10:26Z http://community.qnx.com/sf/go/post70213 If you beat your head against a coconut long enough something is bound to crack. I found out how to rename the umass devices buried in the bowels of the enum-devices config files: devb-umass cam pnp disk name=umass cdrom name=umasscd & This is not documented. But I still can't get mcd to recognize these devices and mount them. Mon, 11 Oct 2010 20:56:08 GMT http://community.qnx.com/sf/go/post70213 Robert Murrell 2010-10-11T20:56:08Z http://community.qnx.com/sf/go/post70212 I should add that I'm developing under QNX version 6.5.0. Mon, 11 Oct 2010 19:46:47 GMT http://community.qnx.com/sf/go/post70212 Robert Murrell 2010-10-11T19:46:47Z http://community.qnx.com/sf/go/post70211 I'm trying to get mcd to auto-detect when a USB memory stick is inserted. My boot image is small and does not use the diskboot program and its associated syinit script. I'm booting from a compact flash card that installs as /dev/hd0 and /dev/hd0t77. I can plug in a USB stick and it shows up as /dev/hd1 and /dev/hd1t6. I tried to configure devb-umass to have it show up as the expected /dev/umass*, but this is poorly documented and I couldn't get it to work. So I tried to trick mcd into mounting it as /fs/us0 with the following configuration: mcd.conf: vvvvvvvvvvvvvvvvvvv [/dev/hd*] Callout = PATH_MEDIA_PROCMGR Argument = /proc/mount Priority = 11,10 Start Rule = MOUNT Stop Rule = UNMOUNT [MOUNT] Callout = MOUNT_FSYS Argument = /etc/mcd.mnt [UNMOUNT] Callout = UNMOUNT_FSYS [/dev/cd*] Callout = CD_MEDIA_IOBLK Argument = 1000,2000 Priority = 11,9 Start Rule = MOUNT Stop Rule = UNMOUNT [/fs/cd*] Callout = PATH_MEDIA_PROCMGR Argument = /proc/mount Priority = 11,10 Start Rule = INSERTED Stop Rule = EJECTED [/fs/usb*] Callout = PATH_MEDIA_PROCMGR Argument = /proc/mount Priority = 11,10 Start Rule = INSERTED Stop Rule = EJECTED [/fs/pfs*] Callout = PATH_MEDIA_PROCMGR Argument = /proc/mount Priority = 11,10 Start Rule = INSERTED Stop Rule = EJECTED [INSERTED] [EJECTED] [AVAILABLE] ^^^^^^^^^^^^^ mcd.mnt: vvvvvvvvvvvvvvvv #---------------------------------------------------------------------- # Device Mountpt Type Options #---------------------------------------------------------------------- /dev/cd[0-9] /fs/cd%# udf normv /dev/hd[1-9] / enum /dev/hd[1-9]t1[124] /fs/usb%0 dos normv,fsi=use /dev/hd[1-9]t1[124].[0-9] /fs/usb%0 dos normv,fsi=use /dev/hd[1-9]t[146] /fs/usb%0 dos normv,fsi=use /dev/hd[1-9]t[146].[0-9] /fs/usb%0 dos normv,fsi=use /dev/hd[1-9]t7[789] /fs/usb%0 qnx4 normv /dev/hd[1-9]t17[789] /fs/usb%0 qnx6 normv,sync=optional /dev/hd[1-9]t7 /fs/usb%0 nt normv,ro /dev/hd[1-9]t175 /fs/usb%0 mac normv,ro /dev/hd[1-9] /fs/usb%0 dos normv,fsi=use ^^^^^^^^^^^^^^^ This doesn't work and I don't see any errors in slogger. If I insert the stick and manually mount the device it shows up: # mount -t dos /dev/hd1t6 /fs/usb0 When I unplug the stick, /fs/usb0 and the devices disappear correctly. Is what I am doing incorrect? Is there a better way? I've attached my build file as generated by the IDE. Rob Murrell Mon, 11 Oct 2010 19:28:00 GMT http://community.qnx.com/sf/go/post70211 Robert Murrell 2010-10-11T19:28:00Z http://community.qnx.com/sf/go/post69190 > -----Message d'origine----- > De : James Kelley [mailto:community-noreply@qnx.com] > Envoyé : 30 septembre 2010 11:18 > À : general-filesystems > Objet : Preselecting and starting the correct partition/drive on the primary > boot loader > > I'm having a problem setting up QNX to automatically boot without a > keyboard or operator intervention. > > I currently have an x86 system setup for data acquisition and need the > system to startup complete and run the software setup rc.local. > > BUT.... > > The system hang on the primary boot loader with the following msg: > > Press F1-F4 to select drive or select partition 1,2 1 Remove de .diskboot file on the second disk/partition > > If I have a keyboard attached and press enter, everything works perfectly > but the system is meant to operate in the field without intervention so how > do I set this up to simply go ahead and select the default and continue > without the keyboard attached (I;m willing to put on a keyboard (although > this seems ridiculous) but the system still seems to wait when first powered > up. > > Stumped > > James Kelley > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post69183 > Thu, 30 Sep 2010 15:51:08 GMT http://community.qnx.com/sf/go/post69190 Mario Charest 2010-09-30T15:51:08Z http://community.qnx.com/sf/go/post69183 I'm having a problem setting up QNX to automatically boot without a keyboard or operator intervention. I currently have an x86 system setup for data acquisition and need the system to startup complete and run the software setup rc.local. BUT.... The system hang on the primary boot loader with the following msg: Press F1-F4 to select drive or select partition 1,2 1 If I have a keyboard attached and press enter, everything works perfectly but the system is meant to operate in the field without intervention so how do I set this up to simply go ahead and select the default and continue without the keyboard attached (I;m willing to put on a keyboard (although this seems ridiculous) but the system still seems to wait when first powered up. Stumped James Kelley Thu, 30 Sep 2010 15:17:29 GMT http://community.qnx.com/sf/go/post69183 James Kelley 2010-09-30T15:17:29Z http://community.qnx.com/sf/go/post67901 > -----Message d'origine----- > De : David Sarrazin [mailto:community-noreply@qnx.com] > Envoyé : 20 septembre 2010 09:55 > À : general-filesystems > Objet : RE: qnx6f max file number > > Each inode requires 128 bytes, so 100M inodes is 12.8GB, plus the indirect > blocks. Finding a free inode in a mostly-full system would be time expensive > at that scale. What you are saying is that you expect your 2TB drive to be > filled up with 10KByte average-sized files. Having said that, I know that the > test group here has a 2TB server set up with 10M inodes. > That would be 20K files ;-) I exaggerated that number a bit to get a good idea. Files will be 400K so 5 millions would be closer to what we need. Can you define 'time expensive'? The hardware driver will operate almost 90% full, with around 100 files new files written and the 100 oldest files deleted. Thanks David. > mkqnx6fs uses the hint of -T to guess at the average file size. The number of > inodes are then selected based on that. > > The (current, but might change) values are: > > Desktop: 1024 byte block, 8 blocks/file > Media: 2048 byte block, 512 blocks/file > Runtime: 1024 byte block, 32blocks/file > > David > > > -----Original Message----- > > From: Mario Charest [mailto:community-noreply@qnx.com] > > Sent: September 20, 2010 9:01 AM > > To: general-filesystems > > Subject: qnx6f max file number > > > > Is it unrealistic or does it have some sort of negative impact to have > > a 2TB disk with qnx6fs and specify something like -i 100M ( 100 > > millions) to mkqnx6fs ? > > > > By the way would be nice if the doc on mkqnx6fs would specify the > > exact numbers use by the -T option. > > > > Thanks > > > > > > > > _______________________________________________ > > > > General > > http://community.qnx.com/sf/go/post67848 > > > > > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post67858 > Mon, 20 Sep 2010 17:51:48 GMT http://community.qnx.com/sf/go/post67901 Mario Charest 2010-09-20T17:51:48Z http://community.qnx.com/sf/go/post67858 Each inode requires 128 bytes, so 100M inodes is 12.8GB, plus the indirect blocks. Finding a free inode in a mostly-full system would be time expensive at that scale. What you are saying is that you expect your 2TB drive to be filled up with 10KByte average-sized files. Having said that, I know that the test group here has a 2TB server set up with 10M inodes. mkqnx6fs uses the hint of -T to guess at the average file size. The number of inodes are then selected based on that. The (current, but might change) values are: Desktop: 1024 byte block, 8 blocks/file Media: 2048 byte block, 512 blocks/file Runtime: 1024 byte block, 32blocks/file David > -----Original Message----- > From: Mario Charest [mailto:community-noreply@qnx.com] > Sent: September 20, 2010 9:01 AM > To: general-filesystems > Subject: qnx6f max file number > > Is it unrealistic or does it have some sort of negative > impact to have a 2TB disk with qnx6fs and specify something > like -i 100M ( 100 millions) to mkqnx6fs ? > > By the way would be nice if the doc on mkqnx6fs would specify > the exact numbers use by the -T option. > > Thanks > > > > _______________________________________________ > > General > http://community.qnx.com/sf/go/post67848 > > Mon, 20 Sep 2010 13:54:41 GMT http://community.qnx.com/sf/go/post67858 David Sarrazin 2010-09-20T13:54:41Z http://community.qnx.com/sf/go/post67848 Is it unrealistic or does it have some sort of negative impact to have a 2TB disk with qnx6fs and specify something like -i 100M ( 100 millions) to mkqnx6fs ? By the way would be nice if the doc on mkqnx6fs would specify the exact numbers use by the -T option. Thanks Mon, 20 Sep 2010 13:00:56 GMT http://community.qnx.com/sf/go/post67848 Mario Charest 2010-09-20T13:00:56Z http://community.qnx.com/sf/go/post65745 Did anyone ever figure this out? I have the same issue Thu, 02 Sep 2010 18:02:30 GMT http://community.qnx.com/sf/go/post65745 Brian Mac 2010-09-02T18:02:30Z http://community.qnx.com/sf/go/post65284 Upgrading the flashdisk`s fimrware made the problem go away. For anyone reading this, model is OCZ Vertex and firmware must be version 1.5 -----Message d'origine----- De : Keith Garvin [mailto:community-noreply@qnx.com] Envoyé : 26 août 2010 23:25 À : general-filesystems Objet : RE: RE: qnx6fs space usage Well this means the problem is not in the file system :) It looks like the drive is actually returning not ready error condition after an attempt to send the sync command, but a brief inspection of the code does not reveal more details. Get the verbosity of the devb-eide driver up to get a better clue as to why it's failing. There are several options to the driver that may help to better identify the root of the problem. Keith -----Original Message----- From: Mario Charest [mailto:community-noreply@qnx.com] Sent: August 26, 2010 8:10 AM To: general-filesystems Subject: Re: RE: qnx6fs space usage > Hello Mario, Mate, > > Mate, your understanding is correct. If the sync=none is set, then > there will be no timed snapshots and the operation you describe below > will likely fail with a disk full message just as you describe. As Mate > suggested changing your setup to perform frequent sync() of the file > system will force a snapshot. > > I would be concerned about the IO errors you are seeing when > sync=optional is used. If you can provide a sloginfo output after the > failure case we might be able to see what is going on. Load the block > device driver with blk verbose=cvbf option so we can get more detailed > information in the slog. > There it is, check at the bottom. devb-eide was restarted a few time as seen in the log. The device is SSD OCZ Vextex. On earlier model of SSD ( ScanDisk ) the same image works fine. The same image installed Time Sev Major Minor Args Aug 26 14:34:22 6 17 0 intrinfo size = 320 entry size = 64 count = 5 Aug 26 14:34:22 6 17 0 base = 0x00000000 num = 7 cascade = 07fffffff intr 48 Aug 26 14:34:22 6 17 0 base = 0x00000007 num = 1 cascade = 07fffffff intr 55 Aug 26 14:34:22 6 17 0 base = 0x00000008 num = 7 cascade = 07fffffff intr 56 Aug 26 14:34:22 6 17 0 base = 0x0000000f num = 1 cascade = 07fffffff intr 63 Aug 26 14:34:22 6 17 0 base = 0x80000000 num = 2 cascade = 07fffffff intr 2 Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr 0 - Size 8 Aug 26 14:34:22 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr 0 - Size 4 Aug 26 14:34:22 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr 0 - Size 8 Aug 26 14:34:22 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr 0 - Size 4 Aug 26 14:34:22 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr ffa0 - Size 10 Aug 26 14:34:22 5 14 0 tcpip starting Aug 26 14:34:22 3 14 0 Using pseudo random generator. See "random" option Aug 26 14:34:22 7 15 0 qnet(L4): qnet_birth(): qnet_init() - calling Aug 26 14:34:22 2 19 0 devb-eide 1.00A (Jul 9 2010 13:54:17) Aug 26 14:34:22 2 5 0 libcam.so (Jul 9 2010 13:53:08) bver 6040207 Aug 26 14:34:22 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:34:22 2 19 0 eide_identify_devices: cmd_addr 0x1f0, cntl_addr 0x3f4, irq 0xe, chnl 0, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 0 status 7c, error 7c Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:34:22 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:34:22 2 19 0 eide_identify_devices: cmd_addr 0x170, cntl_addr 0x374, irq 0xf, chnl 1, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 0 status 7f, error 7f Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 1 status 7f, error 7f Aug 26 14:34:22 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:34:22 2 19 0 eide_identify_devices: cmd_addr 0xec00, cntl_addr 0xe880, irq 0x6, chnl 0, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 0 status 50, error 0 Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:34:22 2 19 0 ata_parse_identify: tid 0, phys 4000 Aug 26 14:34:22 2 19 0 eide_display_identify: mdl OCZ-VERTEX sn 58J0W1I7U339H6VP981Y fw 1.4 tid 0, cable 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 1 Aug 26 14:34:22 2 19 0 eide_init_devices: OCZ-VERTEX path 0, tid 0, udma 5, mdma 2, sdma -1, pio 4, mblk 1 Aug 26 14:34:22 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:34:22 2 19 0 eide_identify_devices: cmd_addr 0xe800, cntl_addr 0xe480, irq 0x6, chnl 1, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 0 status 7f, error ff Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 1 status 7f, error ff Aug 26 14:34:22 2 5 100 cam-disk.so (Jul 9 2010 13:53:14) Aug 26 14:34:23 2 25 0 prof_resmgr_init: Couldn't attach as /dev/profiler: Resource busy Aug 26 14:34:24 1 8 0 phfont: init... Aug 26 14:34:24 1 8 0 phfont: initialized. Aug 26 14:34:24 1 8 0 phfont: '/dev/phfont[<32|64>]' server installed. Aug 26 14:34:24 cron: started Aug 26 14:34:25 5 10 0 TSO disabled for link speed < 1G Aug 26 14:34:33 2 5 0 scsi_interpret_sense (eide ptl-0:0:0): cam_status=c4, scsi_status=2, flag=000000c0, vuflag=0008, cmd=35, error=70, sense=3, asc=c, ascq=0 Aug 26 14:35:41 2 19 0 devb-eide 1.00A (Jul 9 2010 13:54:17) Aug 26 14:35:41 2 5 0 libcam.so (Jul 9 2010 13:53:08) bver 6040207 Aug 26 14:35:41 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:35:41 2 19 0 eide_identify_devices: cmd_addr 0x1f0, cntl_addr 0x3f4, irq 0xe, chnl 0, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 0 status 0, error 0 Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:35:41 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:35:41 2 19 0 eide_identify_devices: cmd_addr 0x170, cntl_addr 0x374, irq 0xf, chnl 1, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 0 status 7f, error 7f Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 1 status 7f, error 7f Aug 26 14:35:41 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:35:41 2 19 0 eide_identify_devices: cmd_addr 0xec00, cntl_addr 0xe880, irq 0x6, chnl 0, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 0 status 50, error 0 Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:35:41 2 19 0 ata_parse_identify: tid 0, phys 4000 Aug 26 14:35:41 2 19 0 eide_display_identify: mdl OCZ-VERTEX sn 58J0W1I7U339H6VP981Y fw 1.4 tid 0, cable 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 1 Aug 26 14:35:41 2 19 0 eide_init_devices: OCZ-VERTEX path 0, tid 0, udma 5, mdma 2, sdma -1, pio 4, mblk 1 Aug 26 14:35:41 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:35:41 2 19 0 eide_identify_devices: cmd_addr 0xe800, cntl_addr 0xe480, irq 0x6, chnl 1, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 0 status 7f, error ff Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 1 status 7f, error ff Aug 26 14:35:41 2 5 100 cam-disk.so (Jul 9 2010 13:53:14) Aug 26 14:35:41 5 4 0 io-blk.so (Jul 9 2010 14:13:11) Aug 26 14:35:41 5 4 0 Slab: cachepage [80 x50 @4:1 ~125] Aug 26 14:35:41 5 4 0 Slab: buf [36 x113 @4:1 ~282] Aug 26 14:35:41 5 4 0 Slab: ioreq [4068 x1 @4:1 ~96] Aug 26 14:35:41 5 4 0 Slab: assoc [28 x145 @4:1 ~362] Aug 26 14:35:41 5 4 0 Buffer Cache: [512M memory allocated] Aug 26 14:35:41 5 4 0 Async-IOdone: enabled [tid 3] Aug 26 14:35:41 5 4 0 Read-Ahead: enabled [4k-256k] Aug 26 14:35:41 5 4 0 Slab: delwri [56 x72 @4:1 ~180] Aug 26 14:35:41 5 4 0 Write-Behind: enabled [3 secs/1 sec] Aug 26 14:35:41 5 4 0 Slab: bmap [32 x127 @4:4 ~317] Aug 26 14:35:41 5 4 0 Bmap Cache: enabled [2048 entries] Aug 26 14:35:41 5 4 0 Slab: ncache [72 x56 @4:12 ~140] Aug 26 14:35:41 5 4 0 Name Cache: enabled [1280 entries] Aug 26 14:35:41 5 4 0 Slab: locking [24 x169 @4:1 ~0] Aug 26 14:35:41 5 4 0 Slab: vnode [136 x29 @4:34 ~110] Aug 26 14:35:41 5 4 0 Vnode Cache: enabled [1024-3072 files] Aug 26 14:35:41 5 4 0 Slab: ocb [72 x56 @4:1 ~140] Aug 26 14:35:41 5 4 0 Thread Pool: enabled [2:6:12 threads] Aug 26 14:35:41 5 4 0 Ramdisk: disabled Aug 26 14:35:41 5 4 0 Attach /dev/hd0 Aug 26 14:35:41 5 4 0 Auto-Attach /dev/hd0t179 Aug 26 14:35:41 5 4 0 Auto-Attach /dev/hd0t178 Aug 26 14:35:41 5 4 0 Auto-Attach /dev/hd0t177 Aug 26 14:36:11 5 4 0 Auto-Unmount /dev/hd0t177 Aug 26 14:36:11 5 4 0 Auto-Unmount /dev/hd0t178 Aug 26 14:36:11 5 4 0 Auto-Unmount /dev/hd0t179 Aug 26 14:36:11 5 4 0 Auto-Unmount /dev/hd0 Aug 26 14:36:11 5 4 0 Detach /dev/hd0 Aug 26 14:37:12 2 19 0 devb-eide 1.00A (Jul 9 2010 13:54:17) Aug 26 14:37:12 2 5 0 libcam.so (Jul 9 2010 13:53:08) bver 6040207 Aug 26 14:37:12 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:37:12 2 19 0 eide_identify_devices: cmd_addr 0x1f0, cntl_addr 0x3f4, irq 0xe, chnl 0, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 0 status 65, error 65 Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 1 status 43, error 43 Aug 26 14:37:12 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:37:12 2 19 0 eide_identify_devices: cmd_addr 0x170, cntl_addr 0x374, irq 0xf, chnl 1, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 0 status 7f, error 7f Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 1 status 7f, error 7f Aug 26 14:37:12 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:37:12 2 19 0 eide_identify_devices: cmd_addr 0xec00, cntl_addr 0xe880, irq 0x6, chnl 0, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 0 status 50, error 0 Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:37:12 2 19 0 ata_parse_identify: tid 0, phys 4000 Aug 26 14:37:12 2 19 0 eide_display_identify: mdl OCZ-VERTEX sn 58J0W1I7U339H6VP981Y fw 1.4 tid 0, cable 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 1 Aug 26 14:37:12 2 19 0 eide_init_devices: OCZ-VERTEX path 0, tid 0, udma 5, mdma 2, sdma -1, pio 4, mblk 1 Aug 26 14:37:12 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:37:12 2 19 0 eide_identify_devices: cmd_addr 0xe800, cntl_addr 0xe480, irq 0x6, chnl 1, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 0 status 7f, error ff Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 1 status 7f, error ff Aug 26 14:37:12 2 5 100 cam-disk.so (Jul 9 2010 13:53:14) Aug 26 14:37:12 5 4 0 io-blk.so (Jul 9 2010 14:13:11) Aug 26 14:37:12 5 4 0 Slab: cachepage [80 x50 @4:1 ~125] Aug 26 14:37:12 5 4 0 Slab: buf [36 x113 @4:1 ~282] Aug 26 14:37:12 5 4 0 Slab: ioreq [4068 x1 @4:1 ~96] Aug 26 14:37:12 5 4 0 Slab: assoc [28 x145 @4:1 ~362] Aug 26 14:37:12 5 4 0 Buffer Cache: [512M memory allocated] Aug 26 14:37:12 5 4 0 Async-IOdone: enabled [tid 3] Aug 26 14:37:12 5 4 0 Read-Ahead: enabled [4k-256k] Aug 26 14:37:12 5 4 0 Slab: delwri [56 x72 @4:1 ~180] Aug 26 14:37:12 5 4 0 Write-Behind: enabled [3 secs/1 sec] Aug 26 14:37:12 5 4 0 Slab: bmap [32 x127 @4:4 ~317] Aug 26 14:37:12 5 4 0 Bmap Cache: enabled [2048 entries] Aug 26 14:37:12 5 4 0 Slab: ncache [72 x56 @4:12 ~140] Aug 26 14:37:12 5 4 0 Name Cache: enabled [1280 entries] Aug 26 14:37:12 5 4 0 Slab: locking [24 x169 @4:1 ~0] Aug 26 14:37:12 5 4 0 Slab: vnode [136 x29 @4:34 ~110] Aug 26 14:37:12 5 4 0 Vnode Cache: enabled [1024-3072 files] Aug 26 14:37:12 5 4 0 Slab: ocb [72 x56 @4:1 ~140] Aug 26 14:37:12 5 4 0 Thread Pool: enabled [2:6:12 threads] Aug 26 14:37:12 5 4 0 Ramdisk: disabled Aug 26 14:37:12 5 4 0 Attach /dev/hd0 Aug 26 14:37:12 5 4 0 Auto-Attach /dev/hd0t179 Aug 26 14:37:12 5 4 0 Auto-Attach /dev/hd0t178 Aug 26 14:37:12 5 4 0 Auto-Attach /dev/hd0t177 Aug 26 14:50:15 5 4 0 Auto-Unmount /dev/hd0t177 Aug 26 14:50:15 5 4 0 Auto-Unmount /dev/hd0t178 Aug 26 14:50:15 5 4 0 Auto-Unmount /dev/hd0t179 Aug 26 14:50:15 5 4 0 Auto-Unmount /dev/hd0 Aug 26 14:50:15 5 4 0 Detach /dev/hd0 Aug 26 14:50:42 2 19 0 devb-eide 1.00A (Jul 9 2010 13:54:17) Aug 26 14:50:42 2 5 0 libcam.so (Jul 9 2010 13:53:08) bver 6040207 Aug 26 14:50:42 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:50:42 2 19 0 eide_identify_devices: cmd_addr 0x1f0, cntl_addr 0x3f4, irq 0xe, chnl 0, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 0 status 76, error 76 Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:50:42 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:50:42 2 19 0 eide_identify_devices: cmd_addr 0x170, cntl_addr 0x374, irq 0xf, chnl 1, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 0 status 7f, error 7f Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 1 status 7f, error 7f Aug 26 14:50:42 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:50:42 2 19 0 eide_identify_devices: cmd_addr 0xec00, cntl_addr 0xe880, irq 0x6, chnl 0, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 0 status 50, error 0 Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:50:42 2 19 0 ata_parse_identify: tid 0, phys 4000 Aug 26 14:50:42 2 19 0 eide_display_identify: mdl OCZ-VERTEX sn 58J0W1I7U339H6VP981Y fw 1.4 tid 0, cable 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 1 Aug 26 14:50:42 2 19 0 eide_init_devices: OCZ-VERTEX path 0, tid 0, udma 5, mdma 2, sdma -1, pio 4, mblk 1 Aug 26 14:50:42 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:50:42 2 19 0 eide_identify_devices: cmd_addr 0xe800, cntl_addr 0xe480, irq 0x6, chnl 1, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 0 status 7f, error ff Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 1 status 7f, error ff Aug 26 14:50:42 2 5 100 cam-disk.so (Jul 9 2010 13:53:14) Aug 26 14:50:42 5 4 0 io-blk.so (Jul 9 2010 14:13:11) Aug 26 14:50:42 5 4 0 Slab: cachepage [80 x50 @4:1 ~125] Aug 26 14:50:42 5 4 0 Slab: buf [36 x113 @4:1 ~282] Aug 26 14:50:42 5 4 0 Slab: ioreq [4068 x1 @4:1 ~96] Aug 26 14:50:42 5 4 0 Slab: assoc [28 x145 @4:1 ~362] Aug 26 14:50:42 5 4 0 Buffer Cache: [512M memory allocated] Aug 26 14:50:42 5 4 0 Async-IOdone: enabled [tid 3] Aug 26 14:50:42 5 4 0 Read-Ahead: enabled [4k-256k] Aug 26 14:50:42 5 4 0 Slab: delwri [56 x72 @4:1 ~180] Aug 26 14:50:42 5 4 0 Write-Behind: enabled [3 secs/1 sec] Aug 26 14:50:42 5 4 0 Slab: bmap [32 x127 @4:4 ~317] Aug 26 14:50:42 5 4 0 Bmap Cache: enabled [2048 entries] Aug 26 14:50:42 5 4 0 Slab: ncache [72 x56 @4:12 ~140] Aug 26 14:50:42 5 4 0 Name Cache: enabled [1280 entries] Aug 26 14:50:42 5 4 0 Slab: locking [24 x169 @4:1 ~0] Aug 26 14:50:42 5 4 0 Slab: vnode [136 x29 @4:34 ~110] Aug 26 14:50:42 5 4 0 Vnode Cache: enabled [1024-3072 files] Aug 26 14:50:42 5 4 0 Slab: ocb [72 x56 @4:1 ~140] Aug 26 14:50:42 5 4 0 Thread Pool: enabled [2:6:12 threads] Aug 26 14:50:42 5 4 0 Ramdisk: disabled Aug 26 14:50:42 5 4 0 Attach /dev/hd0 Aug 26 14:50:42 5 4 0 Auto-Attach /dev/hd0t179 Aug 26 14:50:42 5 4 0 Auto-Attach /dev/hd0t178 Aug 26 14:50:42 5 4 0 Auto-Attach /dev/hd0t177 Aug 26 14:53:24 5 4 0 Slab: qnx6-inode [104 x39 @4:1 ~115] Aug 26 14:53:24 5 4 0 Slab: qnx6-cowblk [152 x26 @4:32 ~109] Aug 26 14:53:24 5 4 0 Mount / on /dev/hd0t179 as qnx6 Aug 26 14:53:34 2 5 0 scsi_interpret_sense (eide ptl-0:0:0): cam_status=c4, scsi_status=2, flag=000000c0, vuflag=0008, cmd=35, error=70, sense=3, asc=c, ascq=0 Aug 26 14:53:34 2 4 0 IO sync error /dev/hd0 blk -1 (5) Aug 26 14:53:34 5 3 1000 fs-qnx6: / snapshots suspended E5 (q6_superblock_update@superblock.c:369) Aug 26 14:53:52 5 4 0 Remount / Aug 26 14:53:54 5 4 0 Remount / Aug 26 14:53:54 5 4 0 Remount / Aug 26 14:53:54 5 4 0 Remount / Aug 26 14:53:54 5 4 0 Remount / Aug 26 14:53:54 5 4 0 Remount / Aug 26 15:03:57 5 4 0 Slab: qnx6-inode [104 x39 @4:1 ~115] Aug 26 15:03:57 5 4 0 Slab: qnx6-cowblk [152 x26 @4:32 ~109] Aug 26 15:03:57 5 4 0 Mount /home on /dev/hd0t178 as qnx6 _______________________________________________ General http://community.qnx.com/sf/go/post64588 _______________________________________________ General http://community.qnx.com/sf/go/post64714 Tue, 31 Aug 2010 18:26:38 GMT http://community.qnx.com/sf/go/post65284 Mario Charest 2010-08-31T18:26:38Z http://community.qnx.com/sf/go/post64877 -----Message d'origine----- De : Keith Garvin [mailto:community-noreply@qnx.com] Envoyé : 26 août 2010 23:25 À : general-filesystems Objet : RE: RE: qnx6fs space usage > Well this means the problem is not in the file system :) It looks like the drive is > actually returning not ready error condition after an attempt to send the sync > command, but a brief inspection of the code does not reveal more details. >Get the verbosity of the devb-eide driver up to get a better clue as >to why it's failing. There are several options to the driver that may >help to better identify the root of the problem. I`ve turn every verbose option I could find. I've discovered there is a more recent firmware for these devices. I will try it out Monday. Time Sev Major Minor Args Aug 27 19:29:33 6 17 0 intrinfo size = 320 entry size = 64 count = 5 Aug 27 19:29:33 6 17 0 base = 0x00000000 num = 7 cascade = 07fffffff intr 48 Aug 27 19:29:33 6 17 0 base = 0x00000007 num = 1 cascade = 07fffffff intr 55 Aug 27 19:29:33 6 17 0 base = 0x00000008 num = 7 cascade = 07fffffff intr 56 Aug 27 19:29:33 6 17 0 base = 0x0000000f num = 1 cascade = 07fffffff intr 63 Aug 27 19:29:33 6 17 0 base = 0x80000000 num = 2 cascade = 07fffffff intr 2 Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 6 17 0 scan_device exiting Aug 27 19:29:33 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr 0 - Size 8 Aug 27 19:29:33 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr 0 - Size 4 Aug 27 19:29:33 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr 0 - Size 8 Aug 27 19:29:33 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr 0 - Size 4 Aug 27 19:29:33 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr ffa0 - Size 10 Aug 27 19:29:33 5 14 0 tcpip starting Aug 27 19:29:33 3 14 0 Using pseudo random generator. See "random" option Aug 27 19:29:33 7 15 0 qnet(L4): qnet_birth(): qnet_init() - calling Aug 27 19:29:33 2 19 0 devb-eide 1.00A (Jul 9 2010 13:54:17) Aug 27 19:29:33 2 5 0 libcam.so (Jul 9 2010 13:53:08) bver 6040207 Aug 27 19:29:33 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 27 19:29:33 2 19 0 eide_identify_devices: cmd_addr 0x1f0, cntl_addr 0x3f4, irq 0xe, chnl 0, udma 5, mdma 2, sdma 0, pio 4 Aug 27 19:29:33 2 19 0 eide_identify_devices: probing dev 0 status 0, error 0 Aug 27 19:29:33 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 27 19:29:33 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 27 19:29:33 2 19 0 eide_identify_devices: cmd_addr 0x170, cntl_addr 0x374, irq 0xf, chnl 1, udma 5, mdma 2, sdma 0, pio 4 Aug 27 19:29:33 2 19 0 eide_identify_devices: probing dev 0 status 7f, error 7f Aug 27 19:29:33 2 19 0 eide_identify_devices: probing dev 1 status 7f, error 7f Aug 27 19:29:33 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 27 19:29:33 2 19 0 eide_identify_devices: cmd_addr 0xec00, cntl_addr 0xe880, irq 0x6, chnl 0, udma 6, mdma 2, sdma 0, pio 4 Aug 27 19:29:33 2 19 0 eide_identify_devices: probing dev 0 status 50, error 0 Aug 27 19:29:33 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 27 19:29:33 2 19 0 ata_parse_identify: tid 0, phys 4000 Aug 27 19:29:33 2 19 0 eide_display_identify: mdl OCZ-VERTEX sn 58J0W1I7U339H6VP981Y fw 1.4 tid 0, cable 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 1 Aug 27 19:29:33 2 19 0 eide_init_devices: OCZ-VERTEX path 0, tid 0, udma 5, mdma 2, sdma -1, pio 4, mblk 1 Aug 27 19:29:33 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 27 19:29:33 2 19 0 eide_identify_devices: cmd_addr 0xe800, cntl_addr 0xe480, irq 0x6, chnl 1, udma 6, mdma 2, sdma 0, pio 4 Aug 27 19:29:33 2 19 0 eide_identify_devices: probing dev 0 status 7f, error ff Aug 27 19:29:33 2 19 0 eide_identify_devices: probing dev 1 status 7f, error ff Aug 27 19:29:33 2 5 100 cam-disk.so (Jul 9 2010 13:53:14) Aug 27 19:29:33 2 25 0 prof_resmgr_init: Couldn't attach as /dev/profiler: Resource busy Aug 27 19:29:34 1 8 0 phfont: init... Aug 27 19:29:34 1 8 0 phfont: initialized. Aug 27 19:29:34 1 8 0 phfont: '/dev/phfont[<32|64>]' server installed. Aug 27 19:29:34 cron: started Aug 27 19:29:43 2 5 0 scsi_interpret_sense (eide ptl-0:0:0): cam_status=c4, scsi_status=2, flag=000000c0, vuflag=0008, cmd=35, error=70, sense=3, asc=c, ascq=0 Aug 27 19:30:31 2 5 0 scsi_interpret_sense (eide ptl-0:0:0): cam_status=c4, scsi_status=2, flag=000000c0, vuflag=0008, cmd=35, error=70, sense=3, asc=c, ascq=0 Aug 27 19:31:17 2 19 0 devb-eide 1.00A (Jul 9 2010 13:54:17) Aug 27 19:31:17 2 5 0 libcam.so (Jul 9 2010 13:53:08) bver 6040207 Aug 27 19:31:17 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 27 19:31:17 2 19 0 eide_identify_devices: cmd_addr 0x1f0, cntl_addr 0x3f4, irq 0xe, chnl 0, udma 5, mdma 2, sdma 0, pio 4 Aug 27 19:31:17 2 19 0 eide_identify_devices: probing dev 0 status 0, error 0 Aug 27 19:31:17 2 19 0 eide_identify_devices: probing dev 1 status 43, error 43 Aug 27 19:31:17 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 27 19:31:17 2 19 0 eide_identify_devices: cmd_addr 0x170, cntl_addr 0x374, irq 0xf, chnl 1, udma 5, mdma 2, sdma 0, pio 4 Aug 27 19:31:17 2 19 0 eide_identify_devices: probing dev 0 status 7f, error 7f Aug 27 19:31:17 2 19 0 eide_identify_devices: probing dev 1 status 7f, error 7f Aug 27 19:31:17 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 27 19:31:17 2 19 0 eide_identify_devices: cmd_addr 0xec00, cntl_addr 0xe880, irq 0x6, chnl 0, udma 6, mdma 2, sdma 0, pio 4 Aug 27 19:31:17 2 19 0 eide_identify_devices: probing dev 0 status 50, error 0 Aug 27 19:31:17 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 27 19:31:17 2 19 0 ata_parse_identify: tid 0, phys 4000 Aug 27 19:31:17 2 19 0 eide_display_identify: mdl OCZ-VERTEX sn 58J0W1I7U339H6VP981Y fw 1.4 tid 0, cable 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 1 Aug 27 19:31:17 2 19 0 eide_init_devices: OCZ-VERTEX path 0, tid 0, udma 5, mdma 2, sdma -1, pio 4, mblk 1 Aug 27 19:31:17 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 27 19:31:17 2 19 0 eide_identify_devices: cmd_addr 0xe800, cntl_addr 0xe480, irq 0x6, chnl 1, udma 6, mdma 2, sdma 0, pio 4 Aug 27 19:31:17 2 19 0 eide_identify_devices: probing dev 0 status 7f, error ff Aug 27 19:31:17 2 19 0 eide_identify_devices: probing dev 1 status 7f, error ff Aug 27 19:31:17 2 5 100 cam-disk.so (Jul 9 2010 13:53:14) Aug 27 19:31:17 5 4 0 io-blk.so (Jul 9 2010 14:13:11) Aug 27 19:31:17 5 4 0 Slab: cachepage [80 x50 @4:1 ~125] Aug 27 19:31:17 5 4 0 Slab: buf [36 x113 @4:1 ~282] Aug 27 19:31:17 5 4 0 Slab: ioreq [4068 x1 @4:1 ~96] Aug 27 19:31:17 5 4 0 Slab: assoc [28 x145 @4:1 ~362] Aug 27 19:31:17 5 4 0 Buffer Cache: [512M memory allocated] Aug 27 19:31:17 5 4 0 Async-IOdone: enabled [tid 3] Aug 27 19:31:17 5 4 0 Read-Ahead: enabled [4k-256k] Aug 27 19:31:17 5 4 0 Slab: delwri [56 x72 @4:1 ~180] Aug 27 19:31:17 5 4 0 Write-Behind: enabled [3 secs/1 sec] Aug 27 19:31:17 5 4 0 Slab: bmap [32 x127 @4:4 ~317] Aug 27 19:31:17 5 4 0 Bmap Cache: enabled [2048 entries] Aug 27 19:31:17 5 4 0 Slab: ncache [72 x56 @4:12 ~140] Aug 27 19:31:17 5 4 0 Name Cache: enabled [1280 entries] Aug 27 19:31:17 5 4 0 Slab: locking [24 x169 @4:1 ~0] Aug 27 19:31:17 5 4 0 Slab: vnode [136 x29 @4:34 ~110] Aug 27 19:31:17 5 4 0 Vnode Cache: enabled [1024-3072 files] Aug 27 19:31:17 5 4 0 Slab: ocb [72 x56 @4:1 ~140] Aug 27 19:31:17 5 4 0 Thread Pool: enabled [2:6:12 threads] Aug 27 19:31:17 5 4 0 Ramdisk: disabled Aug 27 19:31:17 2 5 0 scsi_interpret_sense (eide ptl-0:0:0): cam_status=c4, scsi_status=2, flag=00000040, vuflag=0008, cmd=5a, error=70, sense=5, asc=24, ascq=0 Aug 27 19:31:17 2 5 0 scsi_interpret_sense (eide ptl-0:0:0): cam_status=c4, scsi_status=2, flag=00000040, vuflag=0008, cmd=5a, error=70, sense=5, asc=24, ascq=0 Aug 27 19:31:17 5 4 0 Attach /dev/hd0 Aug 27 19:31:17 5 4 0 IO read /dev/hd0 blks 0..7 Aug 27 19:31:17 5 4 0 Auto-Attach /dev/hd0t179 Aug 27 19:31:17 5 4 0 Auto-Attach /dev/hd0t178 Aug 27 19:31:17 5 4 0 Auto-Attach /dev/hd0t177 Aug 27 19:31:58 5 4 0 Slab: qnx6-inode [104 x39 @4:1 ~115] Aug 27 19:31:58 5 4 0 Slab: qnx6-cowblk [152 x26 @4:32 ~109] Aug 27 19:31:58 5 4 0 IO read /dev/hd0 blks 72..79 Aug 27 19:31:58 5 4 0 IO read /dev/hd0 blks 2104496..2104503 Aug 27 19:31:58 5 4 0 IO read /dev/hd0 blks 152..167 Aug 27 19:31:58 5 4 0 IO read /dev/hd0 blks 168..175 Aug 27 19:31:58 5 4 0 Mount / on /dev/hd0t179 as qnx6 Aug 27 19:31:59 5 4 0 IO read /dev/hd0 blks 262192..262207 Aug 27 19:31:59 5 4 0 IO read /dev/hd0 blks 14648..14655 Aug 27 19:31:59 5 4 0 IO read /dev/hd0 blks 1835088..1835103 Aug 27 19:31:59 5 4 0 IO read /dev/hd0 blks 176..183 Aug 27 19:31:59 5 4 0 IO write /dev/hd0 blks 8487..8494 Aug 27 19:32:02 5 4 0 IO write-behind /dev/hd0 blks 8471..8478 Aug 27 19:32:05 5 4 0 IO read /dev/hd0 blks 14672..14679 Aug 27 19:32:05 5 4 0 IO read /dev/hd0 blks 1854768..1854783 Aug 27 19:32:05 5 4 0 IO read /dev/hd0 blks 12624..12631 Aug 27 19:32:05 5 4 0 IO read /dev/hd0 blks 1358224..1358239 Aug 27 19:32:05 5 4 0 IO read /dev/hd0 blks 14664..14671 Aug 27 19:32:05 5 4 0 IO read /dev/hd0 blks 1853160..1853175 Aug 27 19:32:05 5 4 0 IO read /dev/hd0 blks 12632..12639 Aug 27 19:32:05 5 4 0 IO read /dev/hd0 blks 1364968..1364983 Aug 27 19:32:05 5 4 0 IO read /dev/hd0 blks 1853112..1853127 Aug 27 19:32:05 5 4 0 IO read /dev/hd0 blks 12600..12607 Aug 27 19:32:05 5 4 0 IO read /dev/hd0 blks 1312256..1312271 Aug 27 19:32:05 5 4 0 IO read /dev/hd0 blks 12608..12615 Aug 27 19:32:05 5 4 0 IO read /dev/hd0 blks 1312400..1312407 Aug 27 19:32:05 5 4 0 IO read /dev/hd0 blks 14656..14663 Aug 27 19:32:05 5 4 0 IO read /dev/hd0 blks 2097208..2097223 Aug 27 19:32:05 5 4 0 IO read /dev/hd0 blks 1838704..1838711 Aug 27 19:32:05 5 4 0 IO read-ahead /dev/hd0 blks 1838712..1838719 Aug 27 19:32:05 5 4 0 IO read /dev/hd0 blks 1838720..1838839 Aug 27 19:32:05 5 4 0 IO read /dev/hd0 blks 1838840..1838967 Aug 27 19:32:05 5 4 0 IO read-ahead /dev/hd0 blks 1838968..1839095 Aug 27 19:32:05 5 4 0 IO read-ahead /dev/hd0 blks 1839096..1839111 Aug 27 19:32:05 5 4 0 IO read-ahead /dev/hd0 blks 1839112..1839175 Aug 27 19:32:05 5 4 0 IO read /dev/hd0 blks 1853128..1853135 Aug 27 19:32:05 5 4 0 Remount / Aug 27 19:32:08 5 4 0 IO write-behind /dev/hd0 blks 4295..4302 Aug 27 19:32:08 5 4 0 IO write-behind /dev/hd0 blks 6343..6358 Aug 27 19:32:08 5 4 0 IO write-behind /dev/hd0 blks 8471..8478 Aug 27 19:32:08 5 4 0 IO sync /dev/hd0 Aug 27 19:32:08 2 5 0 scsi_interpret_sense (eide ptl-0:0:0): cam_status=c4, scsi_status=2, flag=000000c0, vuflag=0008, cmd=35, error=70, sense=3, asc=c, ascq=0 Aug 27 19:32:08 2 4 0 IO sync error /dev/hd0 blk -1 (5) Aug 27 19:32:08 5 3 1000 fs-qnx6: / snapshots suspended E5 (q6_superblock_update@superblock.c:369) Aug 27 19:32:11 5 4 0 IO read /dev/hd0 blks 1312392..1312399 Aug 27 19:32:11 5 4 0 Remount / Aug 27 19:32:38 5 4 0 IO read /dev/hd0 blks 1838384..1838391 Aug 27 19:32:38 5 4 0 IO read-ahead /dev/hd0 blks 1838392..1838399 Aug 27 19:32:38 5 4 0 IO read /dev/hd0 blks 1838400..1838407 Aug 27 19:32:38 5 4 0 IO read-ahead /dev/hd0 blks 1838408..1838415 Aug 27 19:32:52 5 4 0 IO read /dev/hd0 blks 1839608..1839623 Fri, 27 Aug 2010 19:46:55 GMT http://community.qnx.com/sf/go/post64877 Mario Charest 2010-08-27T19:46:55Z http://community.qnx.com/sf/go/post64714 Well this means the problem is not in the file system :) It looks like the drive is actually returning not ready error condition after an attempt to send the sync command, but a brief inspection of the code does not reveal more details. Get the verbosity of the devb-eide driver up to get a better clue as to why it's failing. There are several options to the driver that may help to better identify the root of the problem. Keith -----Original Message----- From: Mario Charest [mailto:community-noreply@qnx.com] Sent: August 26, 2010 8:10 AM To: general-filesystems Subject: Re: RE: qnx6fs space usage > Hello Mario, Mate, > > Mate, your understanding is correct. If the sync=none is set, then > there will be no timed snapshots and the operation you describe below > will likely fail with a disk full message just as you describe. As Mate > suggested changing your setup to perform frequent sync() of the file > system will force a snapshot. > > I would be concerned about the IO errors you are seeing when > sync=optional is used. If you can provide a sloginfo output after the > failure case we might be able to see what is going on. Load the block > device driver with blk verbose=cvbf option so we can get more detailed > information in the slog. > There it is, check at the bottom. devb-eide was restarted a few time as seen in the log. The device is SSD OCZ Vextex. On earlier model of SSD ( ScanDisk ) the same image works fine. The same image installed Time Sev Major Minor Args Aug 26 14:34:22 6 17 0 intrinfo size = 320 entry size = 64 count = 5 Aug 26 14:34:22 6 17 0 base = 0x00000000 num = 7 cascade = 07fffffff intr 48 Aug 26 14:34:22 6 17 0 base = 0x00000007 num = 1 cascade = 07fffffff intr 55 Aug 26 14:34:22 6 17 0 base = 0x00000008 num = 7 cascade = 07fffffff intr 56 Aug 26 14:34:22 6 17 0 base = 0x0000000f num = 1 cascade = 07fffffff intr 63 Aug 26 14:34:22 6 17 0 base = 0x80000000 num = 2 cascade = 07fffffff intr 2 Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr 0 - Size 8 Aug 26 14:34:22 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr 0 - Size 4 Aug 26 14:34:22 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr 0 - Size 8 Aug 26 14:34:22 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr 0 - Size 4 Aug 26 14:34:22 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr ffa0 - Size 10 Aug 26 14:34:22 5 14 0 tcpip starting Aug 26 14:34:22 3 14 0 Using pseudo random generator. See "random" option Aug 26 14:34:22 7 15 0 qnet(L4): qnet_birth(): qnet_init() - calling Aug 26 14:34:22 2 19 0 devb-eide 1.00A (Jul 9 2010 13:54:17) Aug 26 14:34:22 2 5 0 libcam.so (Jul 9 2010 13:53:08) bver 6040207 Aug 26 14:34:22 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:34:22 2 19 0 eide_identify_devices: cmd_addr 0x1f0, cntl_addr 0x3f4, irq 0xe, chnl 0, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 0 status 7c, error 7c Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:34:22 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:34:22 2 19 0 eide_identify_devices: cmd_addr 0x170, cntl_addr 0x374, irq 0xf, chnl 1, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 0 status 7f, error 7f Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 1 status 7f, error 7f Aug 26 14:34:22 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:34:22 2 19 0 eide_identify_devices: cmd_addr 0xec00, cntl_addr 0xe880, irq 0x6, chnl 0, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 0 status 50, error 0 Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:34:22 2 19 0 ata_parse_identify: tid 0, phys 4000 Aug 26 14:34:22 2 19 0 eide_display_identify: mdl OCZ-VERTEX sn 58J0W1I7U339H6VP981Y fw 1.4 tid 0, cable 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 1 Aug 26 14:34:22 2 19 0 eide_init_devices: OCZ-VERTEX path 0, tid 0, udma 5, mdma 2, sdma -1, pio 4, mblk 1 Aug 26 14:34:22 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:34:22 2 19 0 eide_identify_devices: cmd_addr 0xe800, cntl_addr 0xe480, irq 0x6, chnl 1, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 0 status 7f, error ff Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 1 status 7f, error ff Aug 26 14:34:22 2 5 100 cam-disk.so (Jul 9 2010 13:53:14) Aug 26 14:34:23 2 25 0 prof_resmgr_init: Couldn't attach as /dev/profiler: Resource busy Aug 26 14:34:24 1 8 0 phfont: init... Aug 26 14:34:24 1 8 0 phfont: initialized. Aug 26 14:34:24 1 8 0 phfont: '/dev/phfont[<32|64>]' server installed. Aug 26 14:34:24 cron: started Aug 26 14:34:25 5 10 0 TSO disabled for link speed < 1G Aug 26 14:34:33 2 5 0 scsi_interpret_sense (eide ptl-0:0:0): cam_status=c4, scsi_status=2, flag=000000c0, vuflag=0008, cmd=35, error=70, sense=3, asc=c, ascq=0 Aug 26 14:35:41 2 19 0 devb-eide 1.00A (Jul 9 2010 13:54:17) Aug 26 14:35:41 2 5 0 libcam.so (Jul 9 2010 13:53:08) bver 6040207 Aug 26 14:35:41 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:35:41 2 19 0 eide_identify_devices: cmd_addr 0x1f0, cntl_addr 0x3f4, irq 0xe, chnl 0, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 0 status 0, error 0 Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:35:41 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:35:41 2 19 0 eide_identify_devices: cmd_addr 0x170, cntl_addr 0x374, irq 0xf, chnl 1, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 0 status 7f, error 7f Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 1 status 7f, error 7f Aug 26 14:35:41 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:35:41 2 19 0 eide_identify_devices: cmd_addr 0xec00, cntl_addr 0xe880, irq 0x6, chnl 0, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 0 status 50, error 0 Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:35:41 2 19 0 ata_parse_identify: tid 0, phys 4000 Aug 26 14:35:41 2 19 0 eide_display_identify: mdl OCZ-VERTEX sn 58J0W1I7U339H6VP981Y fw 1.4 tid 0, cable 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 1 Aug 26 14:35:41 2 19 0 eide_init_devices: OCZ-VERTEX path 0, tid 0, udma 5, mdma 2, sdma -1, pio 4, mblk 1 Aug 26 14:35:41 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:35:41 2 19 0 eide_identify_devices: cmd_addr 0xe800, cntl_addr 0xe480, irq 0x6, chnl 1, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 0 status 7f, error ff Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 1 status 7f, error ff Aug 26 14:35:41 2 5 100 cam-disk.so (Jul 9 2010 13:53:14) Aug 26 14:35:41 5 4 0 io-blk.so (Jul 9 2010 14:13:11) Aug 26 14:35:41 5 4 0 Slab: cachepage [80 x50 @4:1 ~125] Aug 26 14:35:41 5 4 0 Slab: buf [36 x113 @4:1 ~282] Aug 26 14:35:41 5 4 0 Slab: ioreq [4068 x1 @4:1 ~96] Aug 26 14:35:41 5 4 0 Slab: assoc [28 x145 @4:1 ~362] Aug 26 14:35:41 5 4 0 Buffer Cache: [512M memory allocated] Aug 26 14:35:41 5 4 0 Async-IOdone: enabled [tid 3] Aug 26 14:35:41 5 4 0 Read-Ahead: enabled [4k-256k] Aug 26 14:35:41 5 4 0 Slab: delwri [56 x72 @4:1 ~180] Aug 26 14:35:41 5 4 0 Write-Behind: enabled [3 secs/1 sec] Aug 26 14:35:41 5 4 0 Slab: bmap [32 x127 @4:4 ~317] Aug 26 14:35:41 5 4 0 Bmap Cache: enabled [2048 entries] Aug 26 14:35:41 5 4 0 Slab: ncache [72 x56 @4:12 ~140] Aug 26 14:35:41 5 4 0 Name Cache: enabled [1280 entries] Aug 26 14:35:41 5 4 0 Slab: locking [24 x169 @4:1 ~0] Aug 26 14:35:41 5 4 0 Slab: vnode [136 x29 @4:34 ~110] Aug 26 14:35:41 5 4 0 Vnode Cache: enabled [1024-3072 files] Aug 26 14:35:41 5 4 0 Slab: ocb [72 x56 @4:1 ~140] Aug 26 14:35:41 5 4 0 Thread Pool: enabled [2:6:12 threads] Aug 26 14:35:41 5 4 0 Ramdisk: disabled Aug 26 14:35:41 5 4 0 Attach /dev/hd0 Aug 26 14:35:41 5 4 0 Auto-Attach /dev/hd0t179 Aug 26 14:35:41 5 4 0 Auto-Attach /dev/hd0t178 Aug 26 14:35:41 5 4 0 Auto-Attach /dev/hd0t177 Aug 26 14:36:11 5 4 0 Auto-Unmount /dev/hd0t177 Aug 26 14:36:11 5 4 0 Auto-Unmount /dev/hd0t178 Aug 26 14:36:11 5 4 0 Auto-Unmount /dev/hd0t179 Aug 26 14:36:11 5 4 0 Auto-Unmount /dev/hd0 Aug 26 14:36:11 5 4 0 Detach /dev/hd0 Aug 26 14:37:12 2 19 0 devb-eide 1.00A (Jul 9 2010 13:54:17) Aug 26 14:37:12 2 5 0 libcam.so (Jul 9 2010 13:53:08) bver 6040207 Aug 26 14:37:12 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:37:12 2 19 0 eide_identify_devices: cmd_addr 0x1f0, cntl_addr 0x3f4, irq 0xe, chnl 0, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 0 status 65, error 65 Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 1 status 43, error 43 Aug 26 14:37:12 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:37:12 2 19 0 eide_identify_devices: cmd_addr 0x170, cntl_addr 0x374, irq 0xf, chnl 1, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 0 status 7f, error 7f Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 1 status 7f, error 7f Aug 26 14:37:12 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:37:12 2 19 0 eide_identify_devices: cmd_addr 0xec00, cntl_addr 0xe880, irq 0x6, chnl 0, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 0 status 50, error 0 Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:37:12 2 19 0 ata_parse_identify: tid 0, phys 4000 Aug 26 14:37:12 2 19 0 eide_display_identify: mdl OCZ-VERTEX sn 58J0W1I7U339H6VP981Y fw 1.4 tid 0, cable 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 1 Aug 26 14:37:12 2 19 0 eide_init_devices: OCZ-VERTEX path 0, tid 0, udma 5, mdma 2, sdma -1, pio 4, mblk 1 Aug 26 14:37:12 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:37:12 2 19 0 eide_identify_devices: cmd_addr 0xe800, cntl_addr 0xe480, irq 0x6, chnl 1, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 0 status 7f, error ff Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 1 status 7f, error ff Aug 26 14:37:12 2 5 100 cam-disk.so (Jul 9 2010 13:53:14) Aug 26 14:37:12 5 4 0 io-blk.so (Jul 9 2010 14:13:11) Aug 26 14:37:12 5 4 0 Slab: cachepage [80 x50 @4:1 ~125] Aug 26 14:37:12 5 4 0 Slab: buf [36 x113 @4:1 ~282] Aug 26 14:37:12 5 4 0 Slab: ioreq [4068 x1 @4:1 ~96] Aug 26 14:37:12 5 4 0 Slab: assoc [28 x145 @4:1 ~362] Aug 26 14:37:12 5 4 0 Buffer Cache: [512M memory allocated] Aug 26 14:37:12 5 4 0 Async-IOdone: enabled [tid 3] Aug 26 14:37:12 5 4 0 Read-Ahead: enabled [4k-256k] Aug 26 14:37:12 5 4 0 Slab: delwri [56 x72 @4:1 ~180] Aug 26 14:37:12 5 4 0 Write-Behind: enabled [3 secs/1 sec] Aug 26 14:37:12 5 4 0 Slab: bmap [32 x127 @4:4 ~317] Aug 26 14:37:12 5 4 0 Bmap Cache: enabled [2048 entries] Aug 26 14:37:12 5 4 0 Slab: ncache [72 x56 @4:12 ~140] Aug 26 14:37:12 5 4 0 Name Cache: enabled [1280 entries] Aug 26 14:37:12 5 4 0 Slab: locking [24 x169 @4:1 ~0] Aug 26 14:37:12 5 4 0 Slab: vnode [136 x29 @4:34 ~110] Aug 26 14:37:12 5 4 0 Vnode Cache: enabled [1024-3072 files] Aug 26 14:37:12 5 4 0 Slab: ocb [72 x56 @4:1 ~140] Aug 26 14:37:12 5 4 0 Thread Pool: enabled [2:6:12 threads] Aug 26 14:37:12 5 4 0 Ramdisk: disabled Aug 26 14:37:12 5 4 0 Attach /dev/hd0 Aug 26 14:37:12 5 4 0 Auto-Attach /dev/hd0t179 Aug 26 14:37:12 5 4 0 Auto-Attach /dev/hd0t178 Aug 26 14:37:12 5 4 0 Auto-Attach /dev/hd0t177 Aug 26 14:50:15 5 4 0 Auto-Unmount /dev/hd0t177 Aug 26 14:50:15 5 4 0 Auto-Unmount /dev/hd0t178 Aug 26 14:50:15 5 4 0 Auto-Unmount /dev/hd0t179 Aug 26 14:50:15 5 4 0 Auto-Unmount /dev/hd0 Aug 26 14:50:15 5 4 0 Detach /dev/hd0 Aug 26 14:50:42 2 19 0 devb-eide 1.00A (Jul 9 2010 13:54:17) Aug 26 14:50:42 2 5 0 libcam.so (Jul 9 2010 13:53:08) bver 6040207 Aug 26 14:50:42 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:50:42 2 19 0 eide_identify_devices: cmd_addr 0x1f0, cntl_addr 0x3f4, irq 0xe, chnl 0, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 0 status 76, error 76 Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:50:42 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:50:42 2 19 0 eide_identify_devices: cmd_addr 0x170, cntl_addr 0x374, irq 0xf, chnl 1, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 0 status 7f, error 7f Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 1 status 7f, error 7f Aug 26 14:50:42 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:50:42 2 19 0 eide_identify_devices: cmd_addr 0xec00, cntl_addr 0xe880, irq 0x6, chnl 0, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 0 status 50, error 0 Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:50:42 2 19 0 ata_parse_identify: tid 0, phys 4000 Aug 26 14:50:42 2 19 0 eide_display_identify: mdl OCZ-VERTEX sn 58J0W1I7U339H6VP981Y fw 1.4 tid 0, cable 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 1 Aug 26 14:50:42 2 19 0 eide_init_devices: OCZ-VERTEX path 0, tid 0, udma 5, mdma 2, sdma -1, pio 4, mblk 1 Aug 26 14:50:42 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:50:42 2 19 0 eide_identify_devices: cmd_addr 0xe800, cntl_addr 0xe480, irq 0x6, chnl 1, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 0 status 7f, error ff Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 1 status 7f, error ff Aug 26 14:50:42 2 5 100 cam-disk.so (Jul 9 2010 13:53:14) Aug 26 14:50:42 5 4 0 io-blk.so (Jul 9 2010 14:13:11) Aug 26 14:50:42 5 4 0 Slab: cachepage [80 x50 @4:1 ~125] Aug 26 14:50:42 5 4 0 Slab: buf [36 x113 @4:1 ~282] Aug 26 14:50:42 5 4 0 Slab: ioreq [4068 x1 @4:1 ~96] Aug 26 14:50:42 5 4 0 Slab: assoc [28 x145 @4:1 ~362] Aug 26 14:50:42 5 4 0 Buffer Cache: [512M memory allocated] Aug 26 14:50:42 5 4 0 Async-IOdone: enabled [tid 3] Aug 26 14:50:42 5 4 0 Read-Ahead: enabled [4k-256k] Aug 26 14:50:42 5 4 0 Slab: delwri [56 x72 @4:1 ~180] Aug 26 14:50:42 5 4 0 Write-Behind: enabled [3 secs/1 sec] Aug 26 14:50:42 5 4 0 Slab: bmap [32 x127 @4:4 ~317] Aug 26 14:50:42 5 4 0 Bmap Cache: enabled [2048 entries] Aug 26 14:50:42 5 4 0 Slab: ncache [72 x56 @4:12 ~140] Aug 26 14:50:42 5 4 0 Name Cache: enabled [1280 entries] Aug 26 14:50:42 5 4 0 Slab: locking [24 x169 @4:1 ~0] Aug 26 14:50:42 5 4 0 Slab: vnode [136 x29 @4:34 ~110] Aug 26 14:50:42 5 4 0 Vnode Cache: enabled [1024-3072 files] Aug 26 14:50:42 5 4 0 Slab: ocb [72 x56 @4:1 ~140] Aug 26 14:50:42 5 4 0 Thread Pool: enabled [2:6:12 threads] Aug 26 14:50:42 5 4 0 Ramdisk: disabled Aug 26 14:50:42 5 4 0 Attach /dev/hd0 Aug 26 14:50:42 5 4 0 Auto-Attach /dev/hd0t179 Aug 26 14:50:42 5 4 0 Auto-Attach /dev/hd0t178 Aug 26 14:50:42 5 4 0 Auto-Attach /dev/hd0t177 Aug 26 14:53:24 5 4 0 Slab: qnx6-inode [104 x39 @4:1 ~115] Aug 26 14:53:24 5 4 0 Slab: qnx6-cowblk [152 x26 @4:32 ~109] Aug 26 14:53:24 5 4 0 Mount / on /dev/hd0t179 as qnx6 Aug 26 14:53:34 2 5 0 scsi_interpret_sense (eide ptl-0:0:0): cam_status=c4, scsi_status=2, flag=000000c0, vuflag=0008, cmd=35, error=70, sense=3, asc=c, ascq=0 Aug 26 14:53:34 2 4 0 IO sync error /dev/hd0 blk -1 (5) Aug 26 14:53:34 5 3 1000 fs-qnx6: / snapshots suspended E5 (q6_superblock_update@superblock.c:369) Aug 26 14:53:52 5 4 0 Remount / Aug 26 14:53:54 5 4 0 Remount / Aug 26 14:53:54 5 4 0 Remount / Aug 26 14:53:54 5 4 0 Remount / Aug 26 14:53:54 5 4 0 Remount / Aug 26 14:53:54 5 4 0 Remount / Aug 26 15:03:57 5 4 0 Slab: qnx6-inode [104 x39 @4:1 ~115] Aug 26 15:03:57 5 4 0 Slab: qnx6-cowblk [152 x26 @4:32 ~109] Aug 26 15:03:57 5 4 0 Mount /home on /dev/hd0t178 as qnx6 _______________________________________________ General http://community.qnx.com/sf/go/post64588 Fri, 27 Aug 2010 03:24:45 GMT http://community.qnx.com/sf/go/post64714 Keith Garvin 2010-08-27T03:24:45Z http://community.qnx.com/sf/go/post64588 > Hello Mario, Mate, > > Mate, your understanding is correct. If the sync=none is set, then > there will be no timed snapshots and the operation you describe below > will likely fail with a disk full message just as you describe. As Mate > suggested changing your setup to perform frequent sync() of the file > system will force a snapshot. > > I would be concerned about the IO errors you are seeing when > sync=optional is used. If you can provide a sloginfo output after the > failure case we might be able to see what is going on. Load the block > device driver with blk verbose=cvbf option so we can get more detailed > information in the slog. > There it is, check at the bottom. devb-eide was restarted a few time as seen in the log. The device is SSD OCZ Vextex. On earlier model of SSD ( ScanDisk ) the same image works fine. The same image installed Time Sev Major Minor Args Aug 26 14:34:22 6 17 0 intrinfo size = 320 entry size = 64 count = 5 Aug 26 14:34:22 6 17 0 base = 0x00000000 num = 7 cascade = 07fffffff intr 48 Aug 26 14:34:22 6 17 0 base = 0x00000007 num = 1 cascade = 07fffffff intr 55 Aug 26 14:34:22 6 17 0 base = 0x00000008 num = 7 cascade = 07fffffff intr 56 Aug 26 14:34:22 6 17 0 base = 0x0000000f num = 1 cascade = 07fffffff intr 63 Aug 26 14:34:22 6 17 0 base = 0x80000000 num = 2 cascade = 07fffffff intr 2 Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 6 17 0 scan_device exiting Aug 26 14:34:22 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr 0 - Size 8 Aug 26 14:34:22 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr 0 - Size 4 Aug 26 14:34:22 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr 0 - Size 8 Aug 26 14:34:22 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr 0 - Size 4 Aug 26 14:34:22 3 17 0 Range check failed (IO) - Dev 269e - Vend 8086 - Class 1018a - Addr ffa0 - Size 10 Aug 26 14:34:22 5 14 0 tcpip starting Aug 26 14:34:22 3 14 0 Using pseudo random generator. See "random" option Aug 26 14:34:22 7 15 0 qnet(L4): qnet_birth(): qnet_init() - calling Aug 26 14:34:22 2 19 0 devb-eide 1.00A (Jul 9 2010 13:54:17) Aug 26 14:34:22 2 5 0 libcam.so (Jul 9 2010 13:53:08) bver 6040207 Aug 26 14:34:22 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:34:22 2 19 0 eide_identify_devices: cmd_addr 0x1f0, cntl_addr 0x3f4, irq 0xe, chnl 0, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 0 status 7c, error 7c Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:34:22 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:34:22 2 19 0 eide_identify_devices: cmd_addr 0x170, cntl_addr 0x374, irq 0xf, chnl 1, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 0 status 7f, error 7f Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 1 status 7f, error 7f Aug 26 14:34:22 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:34:22 2 19 0 eide_identify_devices: cmd_addr 0xec00, cntl_addr 0xe880, irq 0x6, chnl 0, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 0 status 50, error 0 Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:34:22 2 19 0 ata_parse_identify: tid 0, phys 4000 Aug 26 14:34:22 2 19 0 eide_display_identify: mdl OCZ-VERTEX sn 58J0W1I7U339H6VP981Y fw 1.4 tid 0, cable 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 1 Aug 26 14:34:22 2 19 0 eide_init_devices: OCZ-VERTEX path 0, tid 0, udma 5, mdma 2, sdma -1, pio 4, mblk 1 Aug 26 14:34:22 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:34:22 2 19 0 eide_identify_devices: cmd_addr 0xe800, cntl_addr 0xe480, irq 0x6, chnl 1, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 0 status 7f, error ff Aug 26 14:34:22 2 19 0 eide_identify_devices: probing dev 1 status 7f, error ff Aug 26 14:34:22 2 5 100 cam-disk.so (Jul 9 2010 13:53:14) Aug 26 14:34:23 2 25 0 prof_resmgr_init: Couldn't attach as /dev/profiler: Resource busy Aug 26 14:34:24 1 8 0 phfont: init... Aug 26 14:34:24 1 8 0 phfont: initialized. Aug 26 14:34:24 1 8 0 phfont: '/dev/phfont[<32|64>]' server installed. Aug 26 14:34:24 cron: started Aug 26 14:34:25 5 10 0 TSO disabled for link speed < 1G Aug 26 14:34:33 2 5 0 scsi_interpret_sense (eide ptl-0:0:0): cam_status=c4, scsi_status=2, flag=000000c0, vuflag=0008, cmd=35, error=70, sense=3, asc=c, ascq=0 Aug 26 14:35:41 2 19 0 devb-eide 1.00A (Jul 9 2010 13:54:17) Aug 26 14:35:41 2 5 0 libcam.so (Jul 9 2010 13:53:08) bver 6040207 Aug 26 14:35:41 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:35:41 2 19 0 eide_identify_devices: cmd_addr 0x1f0, cntl_addr 0x3f4, irq 0xe, chnl 0, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 0 status 0, error 0 Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:35:41 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:35:41 2 19 0 eide_identify_devices: cmd_addr 0x170, cntl_addr 0x374, irq 0xf, chnl 1, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 0 status 7f, error 7f Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 1 status 7f, error 7f Aug 26 14:35:41 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:35:41 2 19 0 eide_identify_devices: cmd_addr 0xec00, cntl_addr 0xe880, irq 0x6, chnl 0, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 0 status 50, error 0 Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:35:41 2 19 0 ata_parse_identify: tid 0, phys 4000 Aug 26 14:35:41 2 19 0 eide_display_identify: mdl OCZ-VERTEX sn 58J0W1I7U339H6VP981Y fw 1.4 tid 0, cable 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 1 Aug 26 14:35:41 2 19 0 eide_init_devices: OCZ-VERTEX path 0, tid 0, udma 5, mdma 2, sdma -1, pio 4, mblk 1 Aug 26 14:35:41 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:35:41 2 19 0 eide_identify_devices: cmd_addr 0xe800, cntl_addr 0xe480, irq 0x6, chnl 1, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 0 status 7f, error ff Aug 26 14:35:41 2 19 0 eide_identify_devices: probing dev 1 status 7f, error ff Aug 26 14:35:41 2 5 100 cam-disk.so (Jul 9 2010 13:53:14) Aug 26 14:35:41 5 4 0 io-blk.so (Jul 9 2010 14:13:11) Aug 26 14:35:41 5 4 0 Slab: cachepage [80 x50 @4:1 ~125] Aug 26 14:35:41 5 4 0 Slab: buf [36 x113 @4:1 ~282] Aug 26 14:35:41 5 4 0 Slab: ioreq [4068 x1 @4:1 ~96] Aug 26 14:35:41 5 4 0 Slab: assoc [28 x145 @4:1 ~362] Aug 26 14:35:41 5 4 0 Buffer Cache: [512M memory allocated] Aug 26 14:35:41 5 4 0 Async-IOdone: enabled [tid 3] Aug 26 14:35:41 5 4 0 Read-Ahead: enabled [4k-256k] Aug 26 14:35:41 5 4 0 Slab: delwri [56 x72 @4:1 ~180] Aug 26 14:35:41 5 4 0 Write-Behind: enabled [3 secs/1 sec] Aug 26 14:35:41 5 4 0 Slab: bmap [32 x127 @4:4 ~317] Aug 26 14:35:41 5 4 0 Bmap Cache: enabled [2048 entries] Aug 26 14:35:41 5 4 0 Slab: ncache [72 x56 @4:12 ~140] Aug 26 14:35:41 5 4 0 Name Cache: enabled [1280 entries] Aug 26 14:35:41 5 4 0 Slab: locking [24 x169 @4:1 ~0] Aug 26 14:35:41 5 4 0 Slab: vnode [136 x29 @4:34 ~110] Aug 26 14:35:41 5 4 0 Vnode Cache: enabled [1024-3072 files] Aug 26 14:35:41 5 4 0 Slab: ocb [72 x56 @4:1 ~140] Aug 26 14:35:41 5 4 0 Thread Pool: enabled [2:6:12 threads] Aug 26 14:35:41 5 4 0 Ramdisk: disabled Aug 26 14:35:41 5 4 0 Attach /dev/hd0 Aug 26 14:35:41 5 4 0 Auto-Attach /dev/hd0t179 Aug 26 14:35:41 5 4 0 Auto-Attach /dev/hd0t178 Aug 26 14:35:41 5 4 0 Auto-Attach /dev/hd0t177 Aug 26 14:36:11 5 4 0 Auto-Unmount /dev/hd0t177 Aug 26 14:36:11 5 4 0 Auto-Unmount /dev/hd0t178 Aug 26 14:36:11 5 4 0 Auto-Unmount /dev/hd0t179 Aug 26 14:36:11 5 4 0 Auto-Unmount /dev/hd0 Aug 26 14:36:11 5 4 0 Detach /dev/hd0 Aug 26 14:37:12 2 19 0 devb-eide 1.00A (Jul 9 2010 13:54:17) Aug 26 14:37:12 2 5 0 libcam.so (Jul 9 2010 13:53:08) bver 6040207 Aug 26 14:37:12 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:37:12 2 19 0 eide_identify_devices: cmd_addr 0x1f0, cntl_addr 0x3f4, irq 0xe, chnl 0, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 0 status 65, error 65 Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 1 status 43, error 43 Aug 26 14:37:12 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:37:12 2 19 0 eide_identify_devices: cmd_addr 0x170, cntl_addr 0x374, irq 0xf, chnl 1, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 0 status 7f, error 7f Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 1 status 7f, error 7f Aug 26 14:37:12 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:37:12 2 19 0 eide_identify_devices: cmd_addr 0xec00, cntl_addr 0xe880, irq 0x6, chnl 0, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 0 status 50, error 0 Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:37:12 2 19 0 ata_parse_identify: tid 0, phys 4000 Aug 26 14:37:12 2 19 0 eide_display_identify: mdl OCZ-VERTEX sn 58J0W1I7U339H6VP981Y fw 1.4 tid 0, cable 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 1 Aug 26 14:37:12 2 19 0 eide_init_devices: OCZ-VERTEX path 0, tid 0, udma 5, mdma 2, sdma -1, pio 4, mblk 1 Aug 26 14:37:12 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:37:12 2 19 0 eide_identify_devices: cmd_addr 0xe800, cntl_addr 0xe480, irq 0x6, chnl 1, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 0 status 7f, error ff Aug 26 14:37:12 2 19 0 eide_identify_devices: probing dev 1 status 7f, error ff Aug 26 14:37:12 2 5 100 cam-disk.so (Jul 9 2010 13:53:14) Aug 26 14:37:12 5 4 0 io-blk.so (Jul 9 2010 14:13:11) Aug 26 14:37:12 5 4 0 Slab: cachepage [80 x50 @4:1 ~125] Aug 26 14:37:12 5 4 0 Slab: buf [36 x113 @4:1 ~282] Aug 26 14:37:12 5 4 0 Slab: ioreq [4068 x1 @4:1 ~96] Aug 26 14:37:12 5 4 0 Slab: assoc [28 x145 @4:1 ~362] Aug 26 14:37:12 5 4 0 Buffer Cache: [512M memory allocated] Aug 26 14:37:12 5 4 0 Async-IOdone: enabled [tid 3] Aug 26 14:37:12 5 4 0 Read-Ahead: enabled [4k-256k] Aug 26 14:37:12 5 4 0 Slab: delwri [56 x72 @4:1 ~180] Aug 26 14:37:12 5 4 0 Write-Behind: enabled [3 secs/1 sec] Aug 26 14:37:12 5 4 0 Slab: bmap [32 x127 @4:4 ~317] Aug 26 14:37:12 5 4 0 Bmap Cache: enabled [2048 entries] Aug 26 14:37:12 5 4 0 Slab: ncache [72 x56 @4:12 ~140] Aug 26 14:37:12 5 4 0 Name Cache: enabled [1280 entries] Aug 26 14:37:12 5 4 0 Slab: locking [24 x169 @4:1 ~0] Aug 26 14:37:12 5 4 0 Slab: vnode [136 x29 @4:34 ~110] Aug 26 14:37:12 5 4 0 Vnode Cache: enabled [1024-3072 files] Aug 26 14:37:12 5 4 0 Slab: ocb [72 x56 @4:1 ~140] Aug 26 14:37:12 5 4 0 Thread Pool: enabled [2:6:12 threads] Aug 26 14:37:12 5 4 0 Ramdisk: disabled Aug 26 14:37:12 5 4 0 Attach /dev/hd0 Aug 26 14:37:12 5 4 0 Auto-Attach /dev/hd0t179 Aug 26 14:37:12 5 4 0 Auto-Attach /dev/hd0t178 Aug 26 14:37:12 5 4 0 Auto-Attach /dev/hd0t177 Aug 26 14:50:15 5 4 0 Auto-Unmount /dev/hd0t177 Aug 26 14:50:15 5 4 0 Auto-Unmount /dev/hd0t178 Aug 26 14:50:15 5 4 0 Auto-Unmount /dev/hd0t179 Aug 26 14:50:15 5 4 0 Auto-Unmount /dev/hd0 Aug 26 14:50:15 5 4 0 Detach /dev/hd0 Aug 26 14:50:42 2 19 0 devb-eide 1.00A (Jul 9 2010 13:54:17) Aug 26 14:50:42 2 5 0 libcam.so (Jul 9 2010 13:53:08) bver 6040207 Aug 26 14:50:42 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:50:42 2 19 0 eide_identify_devices: cmd_addr 0x1f0, cntl_addr 0x3f4, irq 0xe, chnl 0, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 0 status 76, error 76 Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:50:42 2 19 0 eide_identify_devices: Intel 63XXESB IDE vid 0x8086, did 0x269e, class 0x1018a rev 9, busno 0, dfunc f9 Aug 26 14:50:42 2 19 0 eide_identify_devices: cmd_addr 0x170, cntl_addr 0x374, irq 0xf, chnl 1, udma 5, mdma 2, sdma 0, pio 4 Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 0 status 7f, error 7f Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 1 status 7f, error 7f Aug 26 14:50:42 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:50:42 2 19 0 eide_identify_devices: cmd_addr 0xec00, cntl_addr 0xe880, irq 0x6, chnl 0, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 0 status 50, error 0 Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0 Aug 26 14:50:42 2 19 0 ata_parse_identify: tid 0, phys 4000 Aug 26 14:50:42 2 19 0 eide_display_identify: mdl OCZ-VERTEX sn 58J0W1I7U339H6VP981Y fw 1.4 tid 0, cable 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 1 Aug 26 14:50:42 2 19 0 eide_init_devices: OCZ-VERTEX path 0, tid 0, udma 5, mdma 2, sdma -1, pio 4, mblk 1 Aug 26 14:50:42 2 19 0 eide_identify_devices: Intel 63XXESB SATA vid 0x8086, did 0x2680, class 0x1018f rev 9, busno 0, dfunc fa Aug 26 14:50:42 2 19 0 eide_identify_devices: cmd_addr 0xe800, cntl_addr 0xe480, irq 0x6, chnl 1, udma 6, mdma 2, sdma 0, pio 4 Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 0 status 7f, error ff Aug 26 14:50:42 2 19 0 eide_identify_devices: probing dev 1 status 7f, error ff Aug 26 14:50:42 2 5 100 cam-disk.so (Jul 9 2010 13:53:14) Aug 26 14:50:42 5 4 0 io-blk.so (Jul 9 2010 14:13:11) Aug 26 14:50:42 5 4 0 Slab: cachepage [80 x50 @4:1 ~125] Aug 26 14:50:42 5 4 0 Slab: buf [36 x113 @4:1 ~282] Aug 26 14:50:42 5 4 0 Slab: ioreq [4068 x1 @4:1 ~96] Aug 26 14:50:42 5 4 0 Slab: assoc [28 x145 @4:1 ~362] Aug 26 14:50:42 5 4 0 Buffer Cache: [512M memory allocated] Aug 26 14:50:42 5 4 0 Async-IOdone: enabled [tid 3] Aug 26 14:50:42 5 4 0 Read-Ahead: enabled [4k-256k] Aug 26 14:50:42 5 4 0 Slab: delwri [56 x72 @4:1 ~180] Aug 26 14:50:42 5 4 0 Write-Behind: enabled [3 secs/1 sec] Aug 26 14:50:42 5 4 0 Slab: bmap [32 x127 @4:4 ~317] Aug 26 14:50:42 5 4 0 Bmap Cache: enabled [2048 entries] Aug 26 14:50:42 5 4 0 Slab: ncache [72 x56 @4:12 ~140] Aug 26 14:50:42 5 4 0 Name Cache: enabled [1280 entries] Aug 26 14:50:42 5 4 0 Slab: locking [24 x169 @4:1 ~0] Aug 26 14:50:42 5 4 0 Slab: vnode [136 x29 @4:34 ~110] Aug 26 14:50:42 5 4 0 Vnode Cache: enabled [1024-3072 files] Aug 26 14:50:42 5 4 0 Slab: ocb [72 x56 @4:1 ~140] Aug 26 14:50:42 5 4 0 Thread Pool: enabled [2:6:12 threads] Aug 26 14:50:42 5 4 0 Ramdisk: disabled Aug 26 14:50:42 5 4 0 Attach /dev/hd0 Aug 26 14:50:42 5 4 0 Auto-Attach /dev/hd0t179 Aug 26 14:50:42 5 4 0 Auto-Attach /dev/hd0t178 Aug 26 14:50:42 5 4 0 Auto-Attach /dev/hd0t177 Aug 26 14:53:24 5 4 0 Slab: qnx6-inode [104 x39 @4:1 ~115] Aug 26 14:53:24 5 4 0 Slab: qnx6-cowblk [152 x26 @4:32 ~109] Aug 26 14:53:24 5 4 0 Mount / on /dev/hd0t179 as qnx6 Aug 26 14:53:34 2 5 0 scsi_interpret_sense (eide ptl-0:0:0): cam_status=c4, scsi_status=2, flag=000000c0, vuflag=0008, cmd=35, error=70, sense=3, asc=c, ascq=0 Aug 26 14:53:34 2 4 0 IO sync error /dev/hd0 blk -1 (5) Aug 26 14:53:34 5 3 1000 fs-qnx6: / snapshots suspended E5 (q6_superblock_update@superblock.c:369) Aug 26 14:53:52 5 4 0 Remount / Aug 26 14:53:54 5 4 0 Remount / Aug 26 14:53:54 5 4 0 Remount / Aug 26 14:53:54 5 4 0 Remount / Aug 26 14:53:54 5 4 0 Remount / Aug 26 14:53:54 5 4 0 Remount / Aug 26 15:03:57 5 4 0 Slab: qnx6-inode [104 x39 @4:1 ~115] Aug 26 15:03:57 5 4 0 Slab: qnx6-cowblk [152 x26 @4:32 ~109] Aug 26 15:03:57 5 4 0 Mount /home on /dev/hd0t178 as qnx6 Thu, 26 Aug 2010 15:10:09 GMT http://community.qnx.com/sf/go/post64588 Mario Charest 2010-08-26T15:10:09Z http://community.qnx.com/sf/go/post64261 Hello Mario, Mate, Mate, your understanding is correct. If the sync=none is set, then there will be no timed snapshots and the operation you describe below will likely fail with a disk full message just as you describe. As Mate suggested changing your setup to perform frequent sync() of the file system will force a snapshot. I would be concerned about the IO errors you are seeing when sync=optional is used. If you can provide a sloginfo output after the failure case we might be able to see what is going on. Load the block device driver with blk verbose=cvbf option so we can get more detailed information in the slog. Keith -----Original Message----- From: Mate Szarvas [mailto:community-noreply@qnx.com] Sent: August 24, 2010 11:08 PM To: general-filesystems Subject: RE: qnx6fs space usage Mario, are you doing any control of snapshots, such as disabling snapshots or changing the automatic snapshots interval (10 seconds by default)? My understanding is that if you try to write 60 megs in a single transaction (without any snapshots being taken in the middle) then you would need 120 megs of disk space because the filesystem maintains two copies until the next snapshot. If your SSD can take 40 megs faster than 10 secs then you may need to split the cp -r and issue a number of sync-s in the middle to reclaim area or, alternatively, reduce the snapshot period of the filesystem. If "cp -r" filling in the empty space takes longer than 10 seconds (and you did not tinker with snapshot periods) than I'd expect an automatic snapshot to happen and free up space. In this case I cannot exaplain what you see and you'll need to get input from someone with more expertise. -- Mate -----Original Message----- From: Mario Charest [mailto:community-noreply@qnx.com] Sent: August 25, 2010 3:40 AM To: general-filesystems Subject: qnx6fs space usage There is a partition of 100Meg, with 60 megs of files in it. An upgrade procedure tries to overwrite all of the 60 megs of files with a newwer version, all with a single cp -r command. However it fails on a disk full error. Is that a side effect of the way the fs works. By the way this is on SSD and we have to use sync=none otherwise with sync=optional it doesn`t work at all ( IO error ). I`m not using the qnx6fs for it`s new power fail safe feature but rather for the ability to support more then 2 boot images. _______________________________________________ General http://community.qnx.com/sf/go/post64206 _______________________________________________ General http://community.qnx.com/sf/go/post64260 Wed, 25 Aug 2010 06:50:15 GMT http://community.qnx.com/sf/go/post64261 Keith Garvin 2010-08-25T06:50:15Z http://community.qnx.com/sf/go/post64260 Mario, are you doing any control of snapshots, such as disabling snapshots or changing the automatic snapshots interval (10 seconds by default)? My understanding is that if you try to write 60 megs in a single transaction (without any snapshots being taken in the middle) then you would need 120 megs of disk space because the filesystem maintains two copies until the next snapshot. If your SSD can take 40 megs faster than 10 secs then you may need to split the cp -r and issue a number of sync-s in the middle to reclaim area or, alternatively, reduce the snapshot period of the filesystem. If "cp -r" filling in the empty space takes longer than 10 seconds (and you did not tinker with snapshot periods) than I'd expect an automatic snapshot to happen and free up space. In this case I cannot exaplain what you see and you'll need to get input from someone with more expertise. -- Mate -----Original Message----- From: Mario Charest [mailto:community-noreply@qnx.com] Sent: August 25, 2010 3:40 AM To: general-filesystems Subject: qnx6fs space usage There is a partition of 100Meg, with 60 megs of files in it. An upgrade procedure tries to overwrite all of the 60 megs of files with a newwer version, all with a single cp -r command. However it fails on a disk full error. Is that a side effect of the way the fs works. By the way this is on SSD and we have to use sync=none otherwise with sync=optional it doesn`t work at all ( IO error ). I`m not using the qnx6fs for it`s new power fail safe feature but rather for the ability to support more then 2 boot images. _______________________________________________ General http://community.qnx.com/sf/go/post64206 Wed, 25 Aug 2010 06:07:56 GMT http://community.qnx.com/sf/go/post64260 Mate Szarvas 2010-08-25T06:07:56Z http://community.qnx.com/sf/go/post64206 There is a partition of 100Meg, with 60 megs of files in it. An upgrade procedure tries to overwrite all of the 60 megs of files with a newwer version, all with a single cp -r command. However it fails on a disk full error. Is that a side effect of the way the fs works. By the way this is on SSD and we have to use sync=none otherwise with sync=optional it doesn`t work at all ( IO error ). I`m not using the qnx6fs for it`s new power fail safe feature but rather for the ability to support more then 2 boot images. Tue, 24 Aug 2010 18:40:01 GMT http://community.qnx.com/sf/go/post64206 Mario Charest 2010-08-24T18:40:01Z http://community.qnx.com/sf/go/post62022 Hello friends, We are designing a board based on mpc8323 processor. It will have 512Mbyte NAND flash, 64Mbytes of DDR Memory and NOR Flash. We will boot QNX from the NOR-Flash. Now we want to make an etfs filesystem image for NAND flash. So far we only have mketfs utility for the windows operating system. Therefore we will create etfs image in windows and then will store etfs image in /home directory of Linux. /home directory will be exported by the NFS server and will be mounted from the QNX running on board to its local namespace /mnt/nfs. Now program created etfs image to NAND flash using etfsctl utility etfsctl -d /dev/etfs2 -S -e -w /mnt/nfs/my_image.etfs –c Now the doubt (question) is that 1) In above step… Will etfsctl, first copy the my_image.etfs image to RAM and then write it to NAND flash? OR Will it read small chunks of image and write them to NAND flash? Because, again if it’s the first case then our board will not have 512Mbytes space to store the entire image. 2) Is mketfs utility available for Linux or QNX-PowerPC arch? Thank you very much Apurva Fri, 06 Aug 2010 14:46:05 GMT http://community.qnx.com/sf/go/post62022 Apurva P 2010-08-06T14:46:05Z http://community.qnx.com/sf/go/post61318 Missed. Updated a graph of "Patched system (Write)". Thanks. Mon, 02 Aug 2010 01:28:10 GMT http://community.qnx.com/sf/go/post61318 Shinichiro Nakamura 2010-08-02T01:28:10Z http://community.qnx.com/sf/go/post61317 Please see the result of the patches. Mon, 02 Aug 2010 00:55:17 GMT http://community.qnx.com/sf/go/post61317 Shinichiro Nakamura 2010-08-02T00:55:17Z