Hi, all
I am writing an installation program under qnx rtp for our application
software, after I partitioned the harddisk in my code, I killed the EDIE
driver and then restart it (from my code )again to let the system recongnize
the newly created partition (for some reason, we don’t want to reboot the
machine). Now I met a problem: access () doesn’t work correctly anymore, but
open () opendir () seems still working fine. It seems to me the action to
kill/restart EIDE driver have some impact to the filesystem, and I doublt
that I may need to do something to the file system before I kill the driver,
but I don’t know what I should do, can anyone offer help with this? Thanks.
Xuedong
“Xuedong Chen” <Xuedong.Chen@IGT.com> wrote in message
news:9g81sh$avh$1@inn.qnx.com…
Hi, all
I am writing an installation program under qnx rtp for our application
software, after I partitioned the harddisk in my code, I killed the EDIE
driver and then restart it (from my code )again to let the system
recongnize
the newly created partition (for some reason, we don’t want to reboot the
machine). Now I met a problem: access () doesn’t work correctly anymore,
but
open () opendir () seems still working fine. It seems to me the action to
kill/restart EIDE driver have some impact to the filesystem, and I doublt
that I may need to do something to the file system before I kill the
driver,
but I don’t know what I should do, can anyone offer help with this?
Thanks.
That’s odd, if you kill devb-eide you basicly killed the whole file system.
How can you access devb-eide again? Do you have two devb-eide running?
Do you umount the various mount point before killing devb-eide?
Xuedong
\
Yes, In my system, I have an customerized EPROM where I included the kernel
and devb-eide inside, so I can still access devb-eide from there
(/proc/boot/devb-eide).
I have two hard disks in my system: one is the master of primary IDE where
qnx rtp was installed; the other is the target hard disk, which is a blank
one sitting on the secondary IDE. Before I kill devb-eide, I tried to umount
the first hard disk, but I didn’t see any difference.
Xuedong
“Mario Charest” <mcharest@zinformatic.com> wrote in message
news:9g89gg$fhb$1@inn.qnx.com…
“Xuedong Chen” <> Xuedong.Chen@IGT.com> > wrote in message
news:9g81sh$avh$> 1@inn.qnx.com> …
Hi, all
I am writing an installation program under qnx rtp for our application
software, after I partitioned the harddisk in my code, I killed the EDIE
driver and then restart it (from my code )again to let the system
recongnize
the newly created partition (for some reason, we don’t want to reboot
the
machine). Now I met a problem: access () doesn’t work correctly anymore,
but
open () opendir () seems still working fine. It seems to me the action
to
kill/restart EIDE driver have some impact to the filesystem, and I
doublt
that I may need to do something to the file system before I kill the
driver,
but I don’t know what I should do, can anyone offer help with this?
Thanks.
That’s odd, if you kill devb-eide you basicly killed the whole file
system.
How can you access devb-eide again? Do you have two devb-eide running?
Do you umount the various mount point before killing devb-eide?
Xuedong
\