Sponsored Content
Full Discussion: OpenSolaris UFS Question
Operating Systems Solaris OpenSolaris UFS Question Post 302838055 by BrentBANKS on Sunday 28th of July 2013 08:47:28 PM
Old 07-28-2013
I am pretty sure I installed it with UFS, but not 100% sure. Even if it is S51K, I don't think there'd be a way to communicate with it, would there?
Quote:
You might try to clone your SVR4 disk and experiment by replacing that 99 by 131
If it were anyother day, I would probably be up for that, but I have experimented with Unix all summer, and every experiment so far has failed. Im not real sure if Im up for trying much more hard disk work. What is the process for cloning the disk?
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

UFS partition

Hi all, I have FreeBSD and Debian in my HD, the FreeBSD partition is very small and I'd like to change. I try to use partition magic but it does not work with UFS parition. Anyone know a good partition software? (1 Reply)
Discussion started by: SeVEn
1 Replies

2. UNIX for Dummies Questions & Answers

solaris File system question ( UFS )

Hello all, I'm ufs file system, how can u use the same disk in another machine with the data in tact? to make it clear, I've an ufs FS in a mount point /file1 ( 8GB). now they decide to reintall the OS. After the reinstall, how can i get the same data as it is? will mounting the disk as /file1... (3 Replies)
Discussion started by: i2admin
3 Replies

3. Solaris

UFS Version

Hi, Can anyone help me. I would like to know the ufs version on solaris 7 & 8. Also i would like to know is there any command to verify it. Regards, Raja (1 Reply)
Discussion started by: RajaRC
1 Replies

4. Solaris

UFS logging

I have a couple of servers where something weird is going on. When I run the command "mount | grep logging" I get something similair to this / on /dev/dsk/c0t0d0s0 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=220000 But when I look at /etc/vfstab I dont... (6 Replies)
Discussion started by: csaunders
6 Replies

5. AIX

Ufs

Hi i have 2 know the full details of unix file systems. some one please help me (1 Reply)
Discussion started by: sathish2win
1 Replies

6. Solaris

UFS filesystem mounted on 2 hosts question

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

7. Solaris

Zones not in ufs

Hi All, I am installing Solaris Kernel Update Patch 2.1 When I am installing , An error message is saying that Non Global Zones is not mounted in ufs. I have two non global zones. When i see in the vfstab , the filesystem in vxfs. I dont know whether it will give any impact... (2 Replies)
Discussion started by: jegaraman
2 Replies

8. Solaris

UFS defragmentation

is there any other/better way to defragment the ufs slice instead of backup+restore? how to tell which slice needs defragmenting? (2 Replies)
Discussion started by: orange47
2 Replies
UFS_DISK_CLOSE(3)					   BSD Library Functions Manual 					 UFS_DISK_CLOSE(3)

NAME
ufs_disk_close, ufs_disk_fillout, ufs_disk_fillout_blank, ufs_disk_write -- open and close userland UFS disks LIBRARY
UFS File System Access Library (libufs, -lufs) SYNOPSIS
#include <sys/param.h> #include <sys/mount.h> #include <ufs/ufs/ufsmount.h> #include <ufs/ufs/dinode.h> #include <ufs/ffs/fs.h> #include <libufs.h> int ufs_disk_close(struct uufsd *disk); int ufs_disk_fillout(struct uufsd *disk, const char *name); int ufs_disk_fillout_blank(struct uufsd *disk, const char *name); int ufs_disk_write(struct uufsd *disk); DESCRIPTION
The ufs_disk_close() function closes a disk and frees internal memory related to it. It does not free the disk structure. The ufs_disk_fillout() and ufs_disk_fillout_blank() functions open a disk specified by name and populate the structure pointed to by disk. The disk is opened read-only. The specified name may be either a mountpoint, a device name or a filesystem image. The ufs_disk_fillout() function assumes there is a valid superblock and will fail if not, whereas the ufs_disk_fillout_blank() function makes no assumptions of that sort. The ufs_disk_write() function attempts to re-open a disk as writable if it is not currently. ERRORS
The function ufs_disk_close() has no failure points. The function ufs_disk_fillout() may fail for any of the reasons ufs_disk_fillout_blank() might, as well as for any reason sbread(3) might. The ufs_disk_fillout_blank() may fail and set errno for any of the errors specified for the library functions open(2), strdup(3). Addition- ally, it may follow the libufs(3) error methodologies in situations where no device could be found to open. The function ufs_disk_write() may fail and set errno for any of the errors specified for the library functions open(2) and stat(2). Namely, it will fail if the disk in question may not be written to. SEE ALSO
open(2), getfsfile(3), libufs(3), sbread(3) HISTORY
These functions first appeared as part of libufs(3) in FreeBSD 5.0. AUTHORS
Juli Mallett <jmallett@FreeBSD.org> BSD
June 4, 2003 BSD
All times are GMT -4. The time now is 06:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy