03-04-2017
I accept that and appreciate why the world has moved to ZFS.
Yes, files can be silently corrupted but, as in the other thread that I referenced, the OP had a system that hung during boot and knew the disk was iffy. I hoped that a 'fsck -o full' would tell him which files had bad spots so he knew which files to rewrite. Hence my discussion about whether there are any other tools to read all used disk space.
Anyway, as always with you j-l, thank you for the comprehensive answer.
This User Gave Thanks to hicksd8 For This Post:
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello !
Does anyone knows which de limit of files in the ufs filesystem in the Solaris 2.6 ??
Danke,
Witt (2 Replies)
Discussion started by: witt
2 Replies
2. Solaris
Hi,
I have a 2,1 TB RAID0 Array (3- 750GB discs).
I have Solaris 10 x86 installed.
When I try to create a volume on this drive I receive the following error:
"
WARNING: /pci@0/pci8086/..../sd@6,0 (sd7) disk capacity is too large for current cbd length
"
I assume I can not format... (5 Replies)
Discussion started by: narrok
5 Replies
3. Solaris
Hi there,
I am trying to mount a SAN volume (which is mapped to solaris sparc) partitioned with ufs filesystem onto a linux (intel processor 64bit) server.
*I have re-compiled the linux kernel t support ufs fstype with ro mount support.
filesystem on solaris:... (3 Replies)
Discussion started by: ilan
3 Replies
4. Solaris
I have two Unix (Solaris) hosts that are both attached to our SAN. They are both presented with the same luns.
What I want to do is have the same UFS filesystem mounted on both hosts at the same time. What I am trying to accomplish is creating a zone that will reside on both hosts but only... (2 Replies)
Discussion started by: beaker457
2 Replies
5. BSD
Hi, I'm new to BSD and would like to create a dual-boot between Solaris Express Community Edition and FreeBSD.
I would just like to know if the Solaris UFS file system can be written to by BSD?
I know that BSD uses UFS2, but I'm hoping that it is backwards compatible with UFS1 provided that... (0 Replies)
Discussion started by: Johnny SSH
0 Replies
6. Solaris
Hi Gurus
I want to know the command & tips regarding, how to increase or decrease inode number of the particular ufs filesystem. Is it possible to do it in a live/production environment.
Regards (3 Replies)
Discussion started by: girish.batra
3 Replies
7. Solaris
What can I fix this issue? I have ran below commands but everything is same.:confused:
WARNING: Last shutdown is later than time on time-of-day chip: check date.
The / file system (/dev/rdsk/c1t0d0s0) is being checked
WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F... (4 Replies)
Discussion started by: getrue
4 Replies
8. Solaris
I need to increase the /var (UFS) filesystem and root disk under veritas control or root disk is encapsulated
# df -k /var
Filesystem kbytes used avail capacity Mounted on
/dev/vx/dsk/var 13241195 12475897 674524 96% /var
# fstyp /dev/vx/dsk/var
ufs
# pkginfo... (1 Reply)
Discussion started by: amity
1 Replies
BADSECT(8) System Manager's Manual BADSECT(8)
NAME
badsect - create files to contain bad sectors
SYNOPSIS
/sbin/badsect sector ...
DESCRIPTION
Badsect makes a file to contain a bad sector. Normally, bad sectors are made inaccessible by the standard formatter, which provides a for-
warding table for bad sectors to the driver; see bad144(8) for details. If a driver supports the bad blocking standard it is much prefer-
able to use that method to isolate bad blocks, since the bad block forwarding makes the pack appear perfect, and such packs can then be
copied with dd(1). The technique used by this program is also less general than bad block forwarding, as badsect can't make amends for bad
blocks in the i-list of file systems or in swap areas.
Adding a sector which is suddenly bad to the bad sector table currently requires the running of the standard DEC formatter, as UNIX does
not supply formatters. Thus to deal with a newly bad block or on disks where the drivers do not support the bad-blocking standard badsect
may be used to good effect.
Badsect is used on a quiet file system in the following way: First mount the file system, and change to its root directory. Make a direc-
tory BAD there and change into it. Run badsect giving as argument all the bad sectors you wish to add. (The sector numbers should be
given as physical disk sectors relative to the beginning of the file system, exactly as the system reports the sector numbers in its con-
sole error messages.) Then 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 will leave the bad sectors in only the BAD files.
Badsect works by giving the specified sector numbers in a mknod(2) system call (after taking into account the filesystem's block size),
creating a regular file whose first block address is the block containing bad sector and whose name is the bad sector number. The file has
0 length, but the check programs will still consider it to contain the block containing the sector. This has the pleasant effect that the
sector is completely inaccessible to the containing file system since it is not available by accessing the file.
SEE ALSO
mknod(2), bad144(8), fsck(8)
BUGS
If both sectors which comprise a (1024 byte) disk block are bad, you should specify only one of them to badsect, as the blocks in the bad
sector files actually cover both (bad) disk sectors.
On the PDP-11, only sector number less than 131072 may be specified on 1024-byte block filesystems, 65536 on 512-byte block filesystems.
This is because only a short int is passed to the system from mknod.
3rd Berkeley Distribution BADSECT(8)