filesystem error

[Rodrigo Letelier]

Hello to All,
I have a HP N9000 with UX11 and a Autoraid. I have tried to form filesystem through sam, including check of archives of so large length, nevertheless at the time of verifying gives it to me following mensage.

# fsck / TYTtempdb fsck: / etc/default/fs is used for determining the cases out system type
cannot open device / TYTtempdb
system check failure, aborting...

Etc/default/fs reviews the content of the file / which contains LOCAL=vxfs

# fstyp / dev/vgtytrd/lvtyttempdb
vxfs

The problem is generated when trying to migrate a device of 400 data base of Mb, which detects error in filesystem


Atte.

Rodrigo Letelier

[Christopher McCray_1]

Hello,

I apologize in advance for not completely understandig your problem, so here goes:

You stated you created the file system through sam. Was there an error message from sam?

on your fsck command, try using the -F vxfs -o full options. What did this say?

When you created the filesystem, did you include the largefiles option, see your fstab, which could, depending on your data, be the problem. The largefiles option allows files over 2Gb in size.

Hope this helps

Chris

[pap]

Hi try to use this command.

fsck -y /dev/vgtytrd/rlvtyttempdb

always use fsck with raw device name.

Before doing fsck on a file system please unmount the file system.

Hopefully it will work.

Thanks,
-pap

[Rodrigo Letelier]

When it creates filesystem was created without errors. In the characteristics of filesystem this marking to allow archives of so large length. The following ones are the exits of the different used commandos:

# bdf |grep "TYTtempdb"
3563520 1976 3338955 0% /TYTtempdb

# fsck -F vxfs /TYTtempdb
cannot open device /TYTtempdb
file system check failure, aborting ...

# grep "TYTtempdb" /etc/fstab
/dev/vgtytrd/lvtyttempdb /TYTtempdb vxfs rw,suid,largefiles,delaylog,datainlog 0 2

# umount /TYTtempdb

# fsck -y /dev/vgtytrd/rlvtyttempdb
file system is clean - log replay is not required

# mount /dev/vgtytrd/lvtyttempdb /TYTtempdb

Atte.

Rodrigo Letelier

[Sanjay_6]

Hi Rodrigo,

Like you have already noticed, you should unmount the filesystem before running fsck on that filesystem. Also you should use the device file to do a fsck and not the mount point or the lv name. you need to specify the complete name with the vg, /dev/vg_name/lv_name

Hope this helps.

Regds

[Rodrigo Letelier]

I thank for its aid to them. Detecting a problem at level of data base, which declared a problem at level of filesystem.

Atte,

Rodrigo Letelier