Project Home
Project Home
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - QNX 6.6.0 on Intel based CPU with SDD drive and Power-Safe filesystem : (5 Items)
   
QNX 6.6.0 on Intel based CPU with SDD drive and Power-Safe filesystem  
I have a SDD drive formatted with partition 179 and mounted as a /tmp directory.
The slogger  -c -s 200k -l /tmp/syslog,4096k   is running fine most of the time and creates /tmp/syslog1 and /tmp/
syslog2 files.

One a while i can notice that the content (size and time stamp) are are changing.

So i went to the  /tmp/directory and deleted syslog2 file (rm syslog2) and just to verify that the file is deleted run 
ls command
TO MY BIG surprise the file still exist , it had different time stamp and the size was nearly 4MB. The content of that 
file  (sloginfo /tmp/syslog2)  made  a sense .

Why the "rm"  command created such a condition on the file system. Should i worry about  the whole file system integrity
? 
Any comments or explanation would be greatly appreciate specially from QNX .

Regards,
Janusz

Re: QNX 6.6.0 on Intel based CPU with SDD drive and Power-Safe filesystem  
Welcome to the wonderful world of union file systems!
You probably have a /tmp (typically a link to /dev/shmem) before
mounting the file system, which then puts its own /tmp directory on top
of the previous one. That previous directory is still there, and any
open file descriptors still point to files under it. When you deleted
the /tmp directory from the file system you re-exposed the /tmp
directory under it.

--Elad

On Fri, 2018-09-14 at 15:08 -0400, Janusz Ruszel wrote:
> I have a SDD drive formatted with partition 179 and mounted as a /tmp
> directory.
> The slogger  -c -s 200k -l /tmp/syslog,4096k   is running fine most
> of the time and creates /tmp/syslog1 and /tmp/syslog2 files.
> 
> One a while i can notice that the content (size and time stamp) are
> are changing.
> 
> So i went to the  /tmp/directory and deleted syslog2 file (rm
> syslog2) and just to verify that the file is deleted run ls command
> TO MY BIG surprise the file still exist , it had different time stamp
> and the size was nearly 4MB. The content of that file  (sloginfo
> /tmp/syslog2)  made  a sense .
> 
> Why the "rm"  command created such a condition on the file system.
> Should i worry about  the whole file system integrity? 
> Any comments or explanation would be greatly appreciate specially
> from QNX .
> 
> Regards,
> Janusz
> 
> 
> 
> 
> 
> _______________________________________________
> 
> OSTech
> http://community.qnx.com/sf/go/post119100
> To cancel your subscription to this discussion, please e-mail ostech-
> core_os-unsubscribe@community.qnx.com
RE: QNX 6.6.0 on Intel based CPU with SDD drive and Power-Safe filesystem  
Hi Elad,
     You made a great point but in my case the /tmp directory is mounted to the separate physical SDD drive  /dev/
hd1t179 remaining directories are mounted from /dev/hd0t179 which also is a SDD drive.


Thanks,
Janusz 


-----Original Message-----
From: Elad Lahav <community-noreply@qnx.com> 
Sent: Friday, September 14, 2018 1:58 PM
To: ostech-core_os@community.qnx.com
Subject: Re: QNX 6.6.0 on Intel based CPU with SDD drive and Power-Safe filesystem

Welcome to the wonderful world of union file systems!
You probably have a /tmp (typically a link to /dev/shmem) before mounting the file system, which then puts its own /tmp 
directory on top of the previous one. That previous directory is still there, and any open file descriptors still point 
to files under it. When you deleted the /tmp directory from the file system you re-exposed the /tmp directory under it.

--Elad

On Fri, 2018-09-14 at 15:08 -0400, Janusz Ruszel wrote:
> I have a SDD drive formatted with partition 179 and mounted as a /tmp 
> directory.
> The slogger  -c -s 200k -l /tmp/syslog,4096k   is running fine most of 
> the time and creates /tmp/syslog1 and /tmp/syslog2 files.
> 
> One a while i can notice that the content (size and time stamp) are 
> are changing.
> 
> So i went to the  /tmp/directory and deleted syslog2 file (rm
> syslog2) and just to verify that the file is deleted run ls command TO 
> MY BIG surprise the file still exist , it had different time stamp and 
> the size was nearly 4MB. The content of that file  (sloginfo
> /tmp/syslog2)  made  a sense .
> 
> Why the "rm"  command created such a condition on the file system.
> Should i worry about  the whole file system integrity? Any comments or 
> explanation would be greatly appreciate specially from QNX .
> 
> Regards,
> Janusz
> 
> 
> 
> 
> 
> _______________________________________________
> 
> OSTech
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcommun
> ity.qnx.com%2Fsf%2Fgo%2Fpost119100&data=02%7C01%7Cjruszel%40lumine
> xcorp.com%7Cc0eeaf61c0a745f58c5608d61a740752%7Ce25a731e35c343c690c466b
> 856e6dd25%7C1%7C0%7C636725482985743814&sdata=I1MQQJr4FyDjX1AvIKo9C
> ta8TPw%2F0D3cJppTj9rinlU%3D&reserved=0
> To cancel your subscription to this discussion, please e-mail ostech- 
> core_os-unsubscribe@community.qnx.com



_______________________________________________

OSTech
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcommunity.qnx.com%2Fsf%2Fgo%2Fpost119101&data=02%7C01%
7Cjruszel%40luminexcorp.com%7Cc0eeaf61c0a745f58c5608d61a740752%7Ce25a731e35c343c690c466b856e6dd25%7C1%7C0%
7C636725482985743814&sdata=NByvPTeGhzT2PXd09lpcDJb%2FOftVIQv3R3SDUrSTCow%3D&reserved=0
To cancel your subscription to this discussion, please e-mail ostech-core_os-unsubscribe@community.qnx.com
Re: QNX 6.6.0 on Intel based CPU with SDD drive and Power-Safe filesystem  
That doesn't matter. The question is whether you have a /tmp directory
before you mount the file system on the SDD drive.

On Fri, 2018-09-14 at 19:05 +0000, Janusz Ruszel wrote:
> Hi Elad,
>      You made a great point but in my case the /tmp directory is
> mounted to the separate physical SDD drive  /dev/hd1t179 remaining
> directories are mounted from /dev/hd0t179 which also is a SDD drive.
> 
> 
> Thanks,
> Janusz 
> 
> 
> -----Original Message-----
> From: Elad Lahav <community-noreply@qnx.com> 
> Sent: Friday, September 14, 2018 1:58 PM
> To: ostech-core_os@community.qnx.com
> Subject: Re: QNX 6.6.0 on Intel based CPU with SDD drive and Power-
> Safe filesystem
> 
> Welcome to the wonderful world of union file systems!
> You probably have a /tmp (typically a link to /dev/shmem) before
> mounting the file system, which then puts its own /tmp directory on
> top of the previous one. That previous directory is still there, and
> any open file descriptors still point to files under it. When you
> deleted the /tmp directory from the file system you re-exposed the
> /tmp directory under it.
> 
> --Elad
> 
> On Fri, 2018-09-14 at 15:08 -0400, Janusz Ruszel wrote:
> > 
> > I have a SDD drive formatted with partition 179 and mounted as a
> > /tmp 
> > directory.
> > The slogger  -c -s 200k -l /tmp/syslog,4096k   is running fine most
> > of 
> > the time and creates /tmp/syslog1 and /tmp/syslog2 files.
> > 
> > One a while i can notice that the content (size and time stamp)
> > are 
> > are changing.
> > 
> > So i went to the  /tmp/directory and deleted syslog2 file (rm
> > syslog2) and just to verify that the file is deleted run ls command
> > TO 
> > MY BIG surprise the file still exist , it had different time stamp
> > and 
> > the size was nearly 4MB. The content of that file  (sloginfo
> > /tmp/syslog2)  made  a sense .
> > 
> > Why the "rm"  command created such a condition on the file system.
> > Should i worry about  the whole file system integrity? Any comments
> > or 
> > explanation would be greatly appreciate specially from QNX .
> > 
> > Regards,
> > Janusz
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > 
> > OSTech
> > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcom
> > mun
> > ity.qnx.com%2Fsf%2Fgo%2Fpost119100&data=02%7C01%7Cjruszel%40lum
> > ine
> > xcorp.com%7Cc0eeaf61c0a745f58c5608d61a740752%7Ce25a731e35c343c690c4
> > 66b
> > 856e6dd25%7C1%7C0%7C636725482985743814&sdata=I1MQQJr4FyDjX1AvIK
> > o9C
> > ta8TPw%2F0D3cJppTj9rinlU%3D&reserved=0
> > To cancel your subscription to this discussion, please e-mail
> > ostech- 
> > core_os-unsubscribe@community.qnx.com
> 
> 
> _______________________________________________
> 
> OSTech
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcommu
> nity.qnx.com%2Fsf%2Fgo%2Fpost119101&data=02%7C01%7Cjruszel%40lumi
> nexcorp.com%7Cc0eeaf61c0a745f58c5608d61a740752%7Ce25a731e35c343c690c4
> 66b856e6dd25%7C1%7C0%7C636725482985743814&sdata=NByvPTeGhzT2PXd09
> lpcDJb%2FOftVIQv3R3SDUrSTCow%3D&reserved=0
> To cancel your subscription to this discussion, please e-mail ostech-
> core_os-unsubscribe@community.qnx.com
> 
> 
> 
> 
> _______________________________________________
> 
> OSTech
> http://community.qnx.com/sf/go/post119103
> To cancel your subscription to this discussion, please e-mail ostech-
> core_os-unsubscribe@community.qnx.com
Re: QNX 6.6.0 on Intel based CPU with SDD drive and Power-Safe filesystem  
Agree!