10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
Hello,
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sr0 11:0 1 1024M 0 rom
sda 8:0 0 38.2G 0 disk
├─sda1 8:1 0 500M 0 part /boot
└─sda2 8:2 ... (2 Replies)
Discussion started by: centosadmin
2 Replies
2. AIX
Hello,
I would like to reduce the size of filesystem online. We can do online for increase without any problem. So any risk can be occurred with the decrease? This is not an issue, just a discussion for decrease/shrink space with chfs command.
My AIX system is version 6.1 and the filesystem... (2 Replies)
Discussion started by: Phat
2 Replies
3. Red Hat
Hello guys,
I would like to ask you kindly if you don't know some quick and safe method how to shrink ext4 filesystem and reduce the size of a Logical Volume in Linux, please?
Thank you very much. (2 Replies)
Discussion started by: los_bandidos
2 Replies
4. SCO
Hi all,
I hope you are fine,
I'd like study Os I tried a book like Silberschatz it's a good book but like
other books it talks about the concepts abstractly and that's due to it try
to encompass many concepts from many operating systems in GENERAL.
i am not too much comfortable from these... (20 Replies)
Discussion started by: Abdo_8008
20 Replies
5. UNIX for Advanced & Expert Users
My root file system is of type LVM. i wanna shrink it but unable to do so.
When i give the below command:
resize2fs /dev/mapper/VolGroup00-VolLog00 10000M
it messages that online shrink can't can't be done as the logical volume is mounted on /. i switched to single user mode by giving command:... (2 Replies)
Discussion started by: ravisingh
2 Replies
6. AIX
When we shrink one of the volume in our IBM Storwize V7000, upto 100GB its shrinks well on storage but the shrink space was not reflected on the volume group, it still shows the same space that it has before shrinking. Should I have to export/import the volume group. (10 Replies)
Discussion started by: m_raheelahmed
10 Replies
7. UNIX for Advanced & Expert Users
I want to backup my partitions by shrinking it my issue is like
I want to create a new disk copy from only the used blocks I my current image.
How would I redirect the output of resize2fs to new disk and dd the current
partition so that I can boot my new image without issues and also without... (3 Replies)
Discussion started by: amol28kulkarni
3 Replies
8. AIX
Hi,
is anyone aware about filesystem size restrictions on AIX? And does anyone know a solution for below problem?
I have 2 boxes attached to EMC Raid5 storage, both have huge /optware/oracle/oradata filesystems - 4.5 and 2.5 TB in size, nothing is striped or in any other way restricted. Due to... (11 Replies)
Discussion started by: zxmaus
11 Replies
9. UNIX for Dummies Questions & Answers
How do I go about switching from one Kernel to another?
I figure the process is somewhat like "compile -> remove old boot reference -> add new boot reference -> reboot/restart kernel"... but honestly I have no idea how to do this...
I'm trying to test out a piece of software, but it only runs... (3 Replies)
Discussion started by: jjinno
3 Replies
10. Solaris
Hi,
Do you know if we can shrink the size of the Swap under Solaris 8 ?
8Gb is already allocated to /TMP but we would like to reduce to 1 GB.
Thanks,
Fabien. (2 Replies)
Discussion started by: unclefab
2 Replies
mem(7D) Devices mem(7D)
NAME
mem, kmem, allkmem - physical or virtual memory access
SYNOPSIS
/dev/mem
/dev/kmem
/dev/allkmem
DESCRIPTION
The file /dev/mem is a special file that provides access to the physical memory of the computer.
The file /dev/kmem is a special file that provides access to the virtual address space of the operating system kernel, excluding memory
that is associated with an I/O device.
The file /dev/allkmem is a special file that provides access to the virtual address space of the operating system kernel, including memory
that is associated with an I/O device. You can use any of these devices to examine and modify the system.
Byte addresses in /dev/mem are interpreted as physical memory addresses. Byte addresses in /dev/kmem and /dev/allkmem are interpreted as
kernel virtual memory addresses. A reference to a non-existent location returns an error. See ERRORS for more information.
The file /dev/mem accesses physical memory; the size of the file is equal to the amount of physical memory in the computer. This size may
be larger than 4GB on a system running the 32-bit operating environment. In this case, you can access memory beyond 4GB using a series of
read(2) and write(2) calls, a pread64() or pwrite64() call, or a combination of llseek(2) and read(2) or write(2).
ERRORS
EFAULT Occurs when trying to write(2) a read-only location (allkmem), read(2) a write-only location (allkmem), or read(2) or
write(2) a non-existent or unimplemented location (mem, kmem, allkmem).
EIO Occurs when trying to read(2) or write(2) a memory location that is associated with an I/O device using the /dev/kmem spe-
cial file.
ENXIO Results from attempting to mmap(2) a non-existent physical (mem) or virtual (kmem, allkmem) memory address.
FILES
/dev/mem Provides access to the computer's physical memory.
/dev/kmem Provides access to the virtual address space of the operating system kernel, excluding memory that is associated with an
I/O device.
/dev/allkmem Provides access to the virtual address space of the operating system kernel, including memory that is associated with an
I/O device.
SEE ALSO
llseek(2), mmap(2), read(2), write(2)
WARNINGS
Using these devices to modify (that is, write to) the address space of a live running operating system or to modify the state of a
hardware device is extremely dangerous and may result in a system panic if kernel data structures are damaged or if device state is
changed.
SunOS 5.10 18 Feb 2002 mem(7D)