File system problem

[Joseph Bague]

Hi to all,

Something weird happening in my B2000, I am running this command but there is no output.

mkfs -F hfs -m /dev/vg00/lvol1

Any idea what is the problem? BTW it is hp-ux 11.00

Regards

Joseph

[T G Manikandan]

First check doing

#vgdisplay -v vg00

and check whether vg01 is already used.

check /var/adm/syslog/syslog.log

[Robert-Jan Goossens]

TGM and Joseph

are you awake :-) think it is /stand

Is your system still running ? if it is do NOT reboot.

Could you check if your still have a kernel in /stand.

# ls -la /stand

Robert-Jan

[Stefan Farrelly]

I think you should be using newfs;

newfs -F hfs /dev/vg00/rlvol1

[Joseph Bague]

Hi T.G.

There is no other vg on that machine other than vg00, and vgdisplay output seems to be fine.

Regards

Joseph

[T G Manikandan]

Robert,Now I am awake,

by default lvol1 in vg00 is taken by the /stand file system.

why are you doing a newfs on that

[T G Manikandan]

Joseph, I meant lvol1 and not vg01 in the previous post!

[Joseph Bague]

Hi Robert

I try this command to my other server this is the sample output.

mkfs -F hfs -L /dev/vg00/lvol1 516096 28 12 65536 8192 16 10 60 10366

I am wondering why is there no output on b2000 (hp-ux 11.00).

Regards

Joseph

[Joseph Bague]

Hi Robert

/stand is still intact.

[Joseph Bague]

according to man mkfs

-m Display the command line that was used to create
the file system. The file system must already
exist. This option provides a means of
determining the parameters used to construct the
file system.

Regards

[Fabio Ettore]

Hi,

as SEP said, why don't you use newfs?
It is better than mkfs, less options, less customizations, less problems:

newfs -F hfs /dev/vg00/rlvol1

Try this command, does it work?

Best regards,
Ettore

[Joseph Bague]

Hi Ettore

I am not trying to format lvol1, what I am trying to do is get some parameter.

Regards

[Fabio Ettore]

Ah....then I understand anything about other posts! :-(

Well, then use

# fsadm -F hfs /dev/vg00/rlvol1
# fstyp -v /dev/vg00/lvol1

Otherwise what is the parameter you are looking for?

Best regards,
Ettore

[Joseph Bague]

Hi

What really happened is my ignite backup is failing, then I send the make.rec1 log to hp engineer. They said ignite backup is calling this command
"mkfs -F hfs -m /dev/vg00/lvol1" (maybe the output is used in automatic recovery script of ignite)which in my b2000 has no output that cause ignite to fail.

regards
Joseph

[Robert-Jan Goossens]

have you tried booting your system in maintenance mode and fsck /stand ?

Robert-Jan

[Fabio Ettore]

Ok Joseph, in order to restrict possible reasons of the problem:
Does mksf work on other filesystems?
Launch it on another filesystem (of course on the same system):
- if mkfs obtains an output then problem is about filesystem; also try other commands (e.g. fstyp or fsadm as I said in my last post);
- if mkfs doesn't obtain an output on other filesystems too then check mkfs size;
# ll /usr/sbin/mkfs
I had a similar problem where a command (I don't remember what it was) was obtaining no output, problem was that it had size 0!

Well, just a thought.... check size of your mkfs. On a my HP-UX 11.00 system I obtain
# ll /usr/sbin/mkfs
lrwxr-xr-x 1 root root 16 Mar 5 2003 /usr/sbin/mkfs -> /sbin/fs_wrapper

What about yours?

Best regards,
Ettore

[Joseph Bague]

Hi Ettore

My answer,

Does mksf work on other filesystems?

--yes, i tried it on /tmp

- if mkfs obtains an output then problem is about filesystem; also try other commands (e.g. fstyp or fsadm as I said in my last post);

-- I tried the fstyp and fsadm on /dev/vg00/lvol1 its ok.

Robert,

Not yet. How can i do it? Does hp-ux mount the /stand on maintenance mode?

Regards
Joseph

[Fabio Ettore]

sorry Joseph if I continue... can you post output of

# ll /usr/sbin/mkfs
# ll /sbin/fs_wrapper

mkfs is linked to fs_wrapper. Check if fs_wrapper or mkfs have size 0. I don't think that it is the problem because mkfs on /tmp filesystem works. I just ask you that for more informations on problems.

Best regards,
Ettore

[Bill Hassell]

Since you are just querying the lvol, then it should work but you might try using the raw volume name (rlvol1 not lvol1). Also, what does the command: lvlnboot -v report? Any problems? Since lvol1 (/stand) is only used for bootup and for building a kernel, first run a backup (just 50-100 megs)then run fsck as in:

umount /stand
fsck -F hfs /dev/vg00/rlvol1
mount /stand


There may be some filesystem corruption causing the hang.