Sponsored Content
Operating Systems Solaris Want to expand Solaris 10_x86 root UFS partition Post 302225464 by Neo on Friday 15th of August 2008 12:37:48 PM
Old 08-15-2008
Quote:
Originally Posted by jlliagre
A kernel panic is worth investigating.
Even if you haven't the skills to analyze them, reporting the issue and sending core/crash dumps on request to the software provider is what I would expect in a professional environment.
What you "expect" is not necessarily the requirement of the user.

Professionally, it is better to give options, and let the user decide what is right, based on their configuration and business model.

Many folks turn off dumps, that is why the option is available. You are making the common mistake (again) of expecting everyone else to follow your best practices without knowledge of their business and/or operational model.
 

10 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

Making a UFS Partition w/ Linux

Well, the subject speaks for itself; how does one go about making a UFS partition in a Linux environment? I don't recall seeing it as an option in my version of fdisk (I'll have to check again when I go home :( ) (6 Replies)
Discussion started by: Karma
6 Replies

3. Solaris

Expand ufs Filesystems

Hi All, I need to expand a number of Filesystems on a Sun machine running Solaris 10 OS. But first I am confused; 1. Is it possible to expand a ufs filesystem such as /dev/dsk/c1t1d0s0 (that is not managed by SVM) without lossing existing data? 2. Is it possible to have such a... (7 Replies)
Discussion started by: atogunde
7 Replies

4. Solaris

how to expand root partition size?

Dear All For installing an application that will seat under /opt , I need to increase my root partition size (/c0t0d0s0) . Can you please let me know how can I increase this partition size? Thank you (10 Replies)
Discussion started by: hadimotamedi
10 Replies

5. Solaris

Mounting UFS partition on multiple servers?

Hi, I have an application on a SAN partition presented to one server only. If I share this SAN partition with a second server as well, will that cause data corruption (the partition is formatted using ufs) ? (5 Replies)
Discussion started by: Mack1982
5 Replies

6. Solaris

Convert root UFS to ZFS on x86 solaris 10/09

Hello All, Good Morning, We are trying to convert the UFS root in to ZFS. Am getting below error. Any one help me out on this ? bash-3.00# zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT guru 5.95G 483M 5.48G 7% ONLINE - bash-3.00# zpool create rpool c2t10d0p0... (4 Replies)
Discussion started by: gowthamakanthan
4 Replies

7. Solaris

Convert UFS (root) to VxFS

Hi all, How to i use vxfs for my server? Because when i install OS, it is installed with ufs, then after Solaris 10 installation, i proceed to install vxfs. How do i convert all the ufs to vxfs? Or is it what i'm doing is the incorrect way? Please help. :wall: (9 Replies)
Discussion started by: beginningDBA
9 Replies

8. Solaris

Need Empty SPARC UFS Partition

Can anyone create a SPARC UFS Partition that is like 50 meg, DD the entire partition and zip it up and send it to me? Trying to play around with creating SPARC UFS partitions on linux and need a real one to compare to. I would do it but I do not have access to a SPARC machine anymore. I do not... (5 Replies)
Discussion started by: mooreps
5 Replies

9. Solaris

Migration of system having UFS root FS with zones root to ZFS root FS

Hi All After downloading ZFS documentation from oracle site, I am able to successfully migrate UFS root FS without zones to ZFS root FS. But in case of UFS root file system with zones , I am successfully able to migrate global zone to zfs root file system but zone are still in UFS root file... (2 Replies)
Discussion started by: sb200
2 Replies

10. Solaris

How to increase the /var (UFS) filesystem and root disk under veritas control?

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
coreadm(1M)															       coreadm(1M)

NAME
coreadm - core file administration SYNOPSIS
pattern] pattern] option] option] [pid...] [pid...] [arguments] [pid...] DESCRIPTION
The command is used for user space application core file management by specifying the name and the location of core files for abnormally terminating processes. See core(4). The command can be used to control system wide and process specific core file placement. The path and pattern is used by the operating system when generating a core file. The first form shown in can be used to control system wide core file settings or specify a pattern for init(1M). System administration privilege is required to change global core file settings. Global core file setting, including the setting for init(1M), is preserved across system reboot. Non-privileged users can change per-process core file settings for processes owned by that user. The real or the effective user ID of the calling process must match the real or the saved user ID of the receiving process unless the effective user ID of the calling process is a user who as appropriate privileges. A core file name pattern is a normal file system path name with embedded variables, specified with a leading character, that are expanded from values in effect when a core file is generated by the operating system. An expanded pattern over will be truncated to The possible pattern variables are: Options The following options are supported for Disable or enable the specified core file option. The and options can only be exercised with root privilege. The valid options for and are: Allow (or disallow) core dumps using the global core pattern. Allow (or disallow) core dumps using the per-process core pattern. Allow (or disallow) core dumps using the global core pattern for processes. Allow (or disallow) core dumps using the process core pattern for processes. Set the global core file name pattern to pattern. The pattern must start with an absolute path name which exists and can contain any of the special % variables described in the section. This option can only be exercised by the super-user. This is identical to specifying a per-process pattern only that the setting is applied to init(1M) and is preserved across reboot. Set the per-process core file name pattern to pattern for each of the specified process-ID's. The pattern can contain any of the special variables described in and need not begin with If it does not begin with the core file name will be evaluated relative to the current working directory at the time of core file creation. This option can be used by non-privileged users to specify core file settings for processes owned by that user. Super-users can apply it to any process. The per-process core file will be inherited by the future child processes of the affected pro- cesses. See fork(2). This option, when invoked without a PID will apply the settings to the calling process (usually the invoking shell). This option is used in conjunction with The option will execute the command specified with the per-process pattern that was specified with This option can be used to enable or disable core file creation for the target process. As an example, a user may choose to add the disable in the shell startup script to avoid creation of core files by that user. EXAMPLES
The following examples assume that the user has appropriate privilege. 1. To examine the current core file settings: $ coreadm global core file pattern: init(1M) core file pattern: global core dumps: disabled per-process core dumps: enabled global setid core dumps: disabled per-process setid core dumps: disabled 2. Set global core file settings to include process-ID and machine name and place the core file in the location $ coreadm -e global -g /mnt/cores/core.%p.%n A process with PID 1777 on the machine breaker will generate a core file in as (in addition to the core file generated in the CWD of PID 1777). 3. Examine the per process core file settings for process-IDs 1777 and 1778 $ coreadm 1777 1778 1777: core.%p.%u 1778: /nethome/gandalf/core/core.%f.%p.%t 4. A user can disable creation of core files completely by specifying in the shell startup file (for example, $ coreadm -P disable $$ $ coreadm $$ 1157: (Disabled) WARNINGS
The output format of may change without notice. Applications parsing the output, should not rely on the compatibility of the output format between releases. SEE ALSO
umask(1), init(1M), coreadm(2), core(4). coreadm(1M)
All times are GMT -4. The time now is 07:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy