02-01-2017
Hi Robin,
I believe the disk is not yet completely faulted but perhaps it is unable to access some sectors which in my opinion already failing.
The burning question is if I may remove the jfs2log on rootvg and recreate it without downtime.
9 More Discussions You Might Find Interesting
1. AIX
New Question:
The purpose of an alternate disk install is in my opinion to have a ready-to-use-backup and i've read that it is possible to install filesets or software on the cloned disk for testing purposal while the normal system is still running.
The question is: how do you tell AIX (5.2... (5 Replies)
Discussion started by: kvanelshocht
5 Replies
2. AIX
Hello
I have a question
I have a box with Aix 5.3 with rootvg on mirror.
I deleted a filesystem and I create a new one to install some software but when I type lsvg -l rootvg all my filesystems has mirror unless the new one.
My question is I can mirror this fs only ??? or I have to... (9 Replies)
Discussion started by: lo-lp-kl
9 Replies
3. AIX
I'm trying to troubleshoot an issue with an AIX system here. I have no experience with system administration of IBM stuff. Our local admin is ... um ... not available at this time.
I found something online that said enter service mode - How the heck do I do that??? Why is IBM stuff lack proper... (2 Replies)
Discussion started by: bbbngowc
2 Replies
4. AIX
When attempting to extend rootvg to a new physical disk I received the following message:
0516-1162 extendvg: Warning, The Physical Partition Size of 64 requires the
creation of 1093 partitions for hdisk5. The limitation for volume group
rootvg is 1016 physical partitions... (4 Replies)
Discussion started by: jyoung
4 Replies
5. AIX
I would like to konw wheather below steps are sufficient for mirroring rootvg.
extendvg rootvg hdisk1
mirrorvg rootvg
bootlist -m normal hdisk0 hdisk1
bosboot -ad hdisk0
bosboot -ad hdisk1
or anything needs to be added. (7 Replies)
Discussion started by: manoj.solaris
7 Replies
6. AIX
I want to increase the size of /tmp by 1GB
I know that the command is
chfs -a size=+1G /tmp
But the rootvg is mirrored and when I do a lsvg -p rootvg, I could see 2 disks.
Will there be any impact if I increase the size of /tmp when the rootvg is mirrored ?
Please advise. (1 Reply)
Discussion started by: newtoaixos
1 Replies
7. AIX
hello everyone, I have an AIX6.1 machine and i want to convert the rootvg to scalable format because i need to increase the size of specific file systems and i cannot do it with its current state. I know that in order to perform this operation the volume group must be varied off so is there a way... (5 Replies)
Discussion started by: omonoiatis9
5 Replies
8. AIX
The root filesystem was mirrored, someone/something stopped mirroring, and increased / and /home to ridiculous values (/ got increased to 102gb and its only using 4.3gb, so 98gb is free). Can I reduce the / (/dev/hd4) filesytem down WITHOUT corrupting the the OS?
I would do a: chfs -a size=10g... (6 Replies)
Discussion started by: mrmurdock
6 Replies
9. UNIX for Beginners Questions & Answers
Hi everybody,
I have a little problem with my AIX 6.1, PowerHA 6.1 LVM mirroring.
I accidentally created logical volume cpsabcd2lv with external jfs2log loglv00 in the same volume group cpsdata2vg. Then I mirrored LV cpsabcd2lv on the second LUN in VG cpsdata2vg. My journal is unmirrored and... (0 Replies)
Discussion started by: Necronomic
0 Replies
badsect(8) System Manager's Manual badsect(8)
NAME
badsect - Creates files to contain bad sectors
SYNOPSIS
/usr/sbin/badsect bbdir sector...
DESCRIPTION
The badsect command makes a file to contain a bad sector. Normally, bad sectors are made inaccessible by the standard formatter, which
provides a forwarding table for bad sectors to the driver. If a driver supports the bad blocking standard, it is preferable to use that
method to isolate bad blocks because the bad block forwarding makes the disk appear perfect, and such disks can then be copied with dd(1).
The technique used by badsect is also less general than bad block forwarding, as badsect cannot make amends for bad blocks in the i-list of
file systems or in swap areas.
On some disks, adding a sector that is suddenly bad to the bad sector table currently requires the running of the standard formatter.
Thus, to deal with a newly bad block or on disks where the drivers do not support the bad-blocking standard, badsect can be used to good
effect.
Use the badsect command on a quiet file system in the following way: Mount the file system and change to its root directory. Make a direc-
tory BAD there. Run badsect, giving as argument the BAD directory followed by all the bad sectors you wish to add. (The sector numbers
must be relative to the beginning of the file system, as reported in console error messages.) Change back to the root directory, unmount
the file system, and run fsck(8) on the file system. The bad sectors should show up in two files or in the bad sector files and the free
list. Have fsck remove files containing the offending bad sectors, but do not have it remove the BAD/nnnnn files. This operation will
leave the bad sectors in only the BAD files.
The badsect command works by giving the specified sector numbers in a mknod(2) system call, creating an illegal file whose first block
address is the block containing bad sector and whose name is the bad sector number. When fsck discovers the file, it will ask "HOLD BAD
BLOCK?" An affirmative response will cause fsck to convert the inode to a regular file containing the bad block.
RESTRICTIONS
If more than one of the sectors comprised by a file system fragment are bad, you should specify only one to badsect, as the blocks in the
bad sector files cover all the sectors in a file system fragment.
ERRORS
The badsect command refuses to attach a block that resides in a critical area or is out of range of the file system. A warning is issued
if the block is already in use.
SEE ALSO
Commands: fsck(8)
badsect(8)