How to remove a "stuck" directory.
bubbawho2002
We have a phone system with VxWorks 5.3.1 on in and it is reporting some IO
errors on a particular directory. When I try an delete it I get the
following:
-> rm "lwoodfor"
value = -1 = 0xffffffff = __func_taskRegsShowRtn + 0xff528e9f
->
I don't have a heck of a lot of experience with VxWorks and the company that
made this is long out of business so any help on how we could remove this
file would be helpful.
Thanks,
Gary
Bill Pringlemeir
Gary> We have a phone system with VxWorks 5.3.1 on in and it is
Gary> reporting some IO errors on a particular directory. When I
Gary> try an delete it I get the following:
-> rm "lwoodfor"
value = -1 = 0xffffffff = __func_taskRegsShowRtn + 0xff528e9f
->
Gary> I don't have a heck of a lot of experience with VxWorks and
Gary> the company that made this is long out of business so any help
Gary> on how we could remove this file would be helpful.
You should be able to type "ioHelp" for some information on the file
system. Are you certain that you are in the directory where the file
is located? Try the command "pwd", "ll", and "chkdsk".
Depending on the version of the file system, the case of the file name
might be important.
hth,
Bill Pringlemeir.
--
Hello, POLICE? I"ve got ABBOTT & COSTELLO here on suspicion of
HIGHWAY ROBBERY!!
Bill Pringlemeir
>>>>> "Gary" == bubbawho2002 <bubbaw...@yahoo.com> writes:
Gary> We have a phone system with VxWorks 5.3.1 on in and it is
Gary> reporting some IO errors on a particular directory. When I
Gary> try an delete it I get the following:
-> rm "lwoodfor"
value = -1 = 0xffffffff = __func_taskRegsShowRtn + 0xff528e9f
->
Gary> I don't have a heck of a lot of experience with VxWorks and
Gary> the company that made this is long out of business so any help
Gary> on how we could remove this file would be helpful.
Bill> You should be able to type "ioHelp" for some information on the
Bill> file system. Are you certain that you are in the directory
Bill> where the file is located? Try the command "pwd", "ll", and
Bill> "chkdsk".
Bill> Depending on the version of the file system, the case of the
Bill> file name might be important.
Opps! I missed the title. If everything else is right, you need
"rmdir" and not "rm". I think that this is standard *nix.
Interesting that "ioHelp" didn't mention "rmdir", "mkdir", etc on my
kernel.
hth,
Bill Pringlemeir.
--
Send your questions to ``ASK ZIPPY'', Box 40474, San Francisco, CA
94140, USA
bubbawho2002
Thanks for the tip. We are definately at the right location for this (did a
pwd to check). Tried rmdir and got this out:
-> rmdir "lwoodfor"
value = -1 = 0xffffffff = __func_taskRegsShowRtn + 0xff528e9f
->
Any other ideas we can try ?
Thanks,
Gary
"Bill Pringlemeir" <spam_a...@sympatico.ca> wrote in message
news:m2vg17o...@sympatico.ca...
Bill Pringlemeir
Gary> Thanks for the tip. We are definately at the right location
Gary> for this (did a pwd to check). Tried rmdir and got this out:
-> rmdir "lwoodfor"
value = -1 = 0xffffffff = __func_taskRegsShowRtn + 0xff528e9f
Gary> Any other ideas we can try ?
What does ll "lwoodfor" do when typed at the same place? Can you show
the details on the file, like size, date, etc. You can try running
"chkdsk 0,0" to see if the file system has any errors. You could also
try,
-> mkdir "myTest"
-> ll
-> pwd
-> rmdir "myTest"
and post the output. Try the same thing in a directory other than
"lwoodfor"... these things will alter your disk (whatever it might
be). It could be that the directory that "lwoodfor" is in has some
sort of directory corruption, etc. The DosFs file system that comes
with vxWorks is based on DOS FAT. Typing "devs" and posting that
output might also be useful. If you have a hard disk, it could be
removed and fixed on a PC. If you have flash (tffs), that would be
worth knowing... as well as your CPU details.
hth,
Bill Pringlemeir.
--
Food is in the air. As Mercury moves into Leo, be careful of your
relationship with your coworker. Don't let a wallflower eat worms
with your abode. You will meet two other people put together this
week. You'll soon be a Borg. Don't forget, it's only 366 days at
most until Christmas.
Bill Pringlemeir
Gary> Thanks for the tip. We are definately at the right location
Gary> for this (did a pwd to check). Tried rmdir and got this out:
-> rmdir "lwoodfor"
value = -1 = 0xffffffff = __func_taskRegsShowRtn + 0xff528e9f
Gary> Any other ideas we can try ?
Bill> What does ll "lwoodfor" do when typed at the same place? Can
Bill> you show the details on the file, like size, date, etc. You
[snip]
Now for something simple... If you have file in the directory you can
not remove it. You have to use,
-> cd "lwoodfor"
-> xdelete "*.*"
-> ll
-> cd ".."
-> rmdir "lwoodfor"
The directory must be empty. This will destroy all of the files. You
can use the command `copy "file"' to diplay a file. You can also make
another directory and copy the files there for backup before deleting
them.
hth,
Bill Pringlemeir.
--
BLU-97 A/B plutonium cypherpunk tempest class struggle secure Perl-RSA
keyhole sweep militia MD2 IMF Leitrim freedom spies
bubbawho2002
I tried adding and removing a directory no problem there, I also tried the
following :
-> pwd
/hd0/shasta/usr/home
value = 21 = 0x15
-> ll "lwoodfor"
Can't open "lwoodfor".
value = -1 = 0xffffffff = __func_taskRegsShowRtn + 0xff528e9f
value = 0 = 0x0
-> ls
Can't open ".".
value = -1 = 0xffffffff = __func_taskRegsShowRtn + 0xff528e9f
Can't open ".".
value = -1 = 0xffffffff = __func_taskRegsShowRtn + 0xff528e9f
Does VxWorks have a file repair utility such as Checkdsk ? I'd really like
to avoid rebuilding this machine for a couple of bad files.
Thanks,
Gary
"Bill Pringlemeir" <spam_a...@sympatico.ca> wrote in message
news:m2vg17i...@sympatico.ca...
Bill Pringlemeir
Gary> Does VxWorks have a file repair utility such as Checkdsk ? I'd
Gary> really like to avoid rebuilding this machine for a couple of
Gary> bad files.
Yes, vxWorks has a chkdsk. I mentioned it in previous posts.
`chkdsk' could possibly do something bad to your disk. If you don't
mind bad things happening (I doubt they will, but you never know),
then you can run `->chkdsk "hd0",2,0x200'. The `->devs' command will
list devices. Yours appears to have some sort of hard drive and the
device is called "hd0". Another name is `iosDevShow'. However, it is
possible that devs/iosDevShow isn't compiled into your system.
hth,
Bill Pringlemeir.
--
Don't forget to have your child spayed or neutered. Tomorrow is not a
good time for sleeping. Months from now talking with piglet3 may seem
like a positive step in the right direction. Today a small bomb would
be a good thing to think about. You'll eventually be confused.
Georg Löffelmann
news:v19gagq...@corp.supernews.com...
...
> /hd0/shasta/usr/home
...
Hi!
Aren't Shasta-Nodes now sold by Nortel Networks? IMHO the Shasta 5000 (which
makes a perfect Gateway GPRS Support Node GGSN) is not _that_ outdated and
in service all over the world. Or is "/shasta" just a coincidence?
BR/
George
Leonid Rosenboim
Isuggest you use a full path, that begins with the device name,
which appears in the output of the "devs" command, e.g. instead of
-> rmdir "/woodfor"
you should do:
-> rmdir "/hd0/woodfor"
Also, make sure the directory exists, and is empty, by listing it, again
using full path:
-> ll "/hd0/woodfor"
If this does not work, you may want to take a look at the directory's
attributes - it could have bene marked read-only, this should be part of
"ll" output.
And regarding "chkdsk", all you need to do is
-> chkdsk "/dh0"
Fro the output of the above commands I could tell you more, e.g. which
version of dosFs you are using.
--
-----------------------------------------------------------------------
Leonid Rosenboim Visit: http://www.masada2000.org/historical.html
Consultant Email: my first name at consultant dot com
"bubbawho2002" <bubbaw...@yahoo.com> wrote in message
news:v18p4eo...@corp.supernews.com...
bubbawho2002
There are files in the directory, however the os reports an IO error when
you try to ll them:
-> ll
size date time name
-------- ------ ------ --------
512 JAN-02-2003 10:41:38 . <DIR>
512 FEB-06-2106 01:28:53 .. <DIR>
512 FEB-06-2106 01:28:33 admin <DIR>
512 FEB-06-2106 01:28:33 DefaultCOS <DIR>
512 FEB-06-2106 01:28:33 defDept <DIR>
512 FEB-06-2106 01:28:33 ftp <DIR>
512 FEB-06-2106 01:28:33 recept <DIR>
512 MAR-11-2002 13:59:14 system <DIR>
512 FEB-06-2106 01:28:36 vmail <DIR>
512 FEB-06-2106 01:28:36 GGauvin <DIR>
512 FEB-06-2106 01:28:37 SGauvin <DIR>
512 FEB-06-2106 01:28:37 MPfiefer <DIR>
512 FEB-06-2106 01:28:38 MAuxilia <DIR>
512 FEB-06-2106 01:28:38 CompanyCOS <DIR>
512 FEB-06-2106 01:28:38 fax0 <DIR>
512 FEB-06-2106 01:28:38 opmh <DIR>
512 FEB-06-2106 01:28:38 remoteAccess <DIR>
512 FEB-06-2106 01:28:39 sales <DIR>
512 FEB-06-2106 01:28:40 spackard <DIR>
512 DEC-06-2002 10:19:41 customer <DIR>
512 FEB-10-2002 15:34:14 kkenyon <DIR>
IO Error - can't stat file: errno = 0x16
0 lwoodfor <IO Error>
512 SEP-10-2002 10:20:43 rfox <DIR>
value = 0 = 0x0
/hd0/shasta/usr/home
value = 21 = 0x15
value = -1 = 0xffffffff = __func_taskRegsShowRtn + 0xff528e9f
->
"Leonid Rosenboim" <My_1s...@Consultant.Com> wrote in message
news:newscache$ttz48h$dle$1...@lnews.actcom.co.il...
Leonid Rosenboim
1. You are running the old dosFs 1.0 (unknown patch level, if any)
2. The failure to get "stat" unfo on the specific entry (which could be
either directory or file) with errno 0x16 (decimal 22) - EINVAL, and that
means something is wrong with that directory entry. Definitely something
that chkdsk would take care of.
What has not been established is availability of chkdsk on your system -
with dosFs 1.0, chkdsk was not part of the package, it was a 3rd party
protuct until 1997 when the vendor was acquired by WindRiver, and then
ht was available from Wind River on an unsupported basis.
In order to find if you have got it do:
-> lkup "chkdsk"
--
-----------------------------------------------------------------------
Leonid Rosenboim Visit: http://www.masada2000.org/historical.html
Consultant Email: my first name at consultant dot com
"bubbawho2002" <bubbaw...@yahoo.com> wrote in message
news:v1be69e...@corp.supernews.com...
bubbawho2002
This is what I was able to retrieve for information on the version and the
result of the lkup command:
-> lkup "chkdsk"
value = 0 = 0x0
VxWorks (for PC 486) version 5.3.1.
Kernel: WIND version 2.5.
Made on Jul 31 2001, 18:10:53.
Boot line:
ata=(0,0):/ata0/vxWorks.st e=10.0.0.0:FFFFFF00 o=/hd0/shasta
PRAXON PDX S/W version 2.0 (1.51) ST
value = 7366696 = 0x706828 = _pxVersionString
->
"Leonid Rosenboim" <My_1s...@Consultant.Com> wrote in message
news:newscache$3ce58h$s8f$1...@lnews.actcom.co.il...
Leonid Rosenboim
"chkdsk for VxWorks" buyout license. No wonder they went belly up.
If the machine uses common FDISK type partition table (which you can't be
sure of), you could remove the hard disk from the machine, hook it up to a
PC and get it cleaned.
--
-----------------------------------------------------------------------
Leonid Rosenboim Visit: http://www.masada2000.org/historical.html
Consultant Email: my first name at consultant dot com
"bubbawho2002" <bubbaw...@yahoo.com> wrote in message
news:v1bjiat...@corp.supernews.com...
Gary H
To remove a directory on this box you need to use the following
command:
RmDir "lwoodfor"
Note the case.
If the directory is damaged, you may have a problem with this command.
The filesystem is not DOS as another user mentioned, but HTFS. There
are up to three partitions on this machine. With no flash card in the
machine,
only the DOS and HTFS partitions are available (as /fat0 and /hd0).
If the filesystem is damaged and fsck does not fix it, you should do a
full
system backup and format the drive using the "setup" command (at the
vxworks
prompt - answer y,y,n to the three questions) and use the system
restore function to restore your backup.
Gary
"bubbawho2002" <bubbaw...@yahoo.com> wrote in message news:<v18p4eo...@corp.supernews.com>...