Sponsored Content
Top Forums UNIX for Advanced & Expert Users How to view Ramdisk Initialization Process Post 302537929 by Hannibal2010 on Monday 11th of July 2011 05:24:51 AM
Old 07-11-2011
How to view Ramdisk Initialization Process

Dear all,

I read some articles about initrd, but how to view this process in my computer Smilie?

Is there anyway to display to the screen or write to the log file?
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix ramdisk?

This may be a stupid question but I've noticed that there is quite a bit out there currently for a ramdisk on that Redmond company's OS. Is there a ramdisk made for Unix and if not, why? (6 Replies)
Discussion started by: keelba
6 Replies

2. UNIX for Dummies Questions & Answers

how to view my own process in a multiuser envrionment

Hi , I am new to unix , tell me how can I check which all are the processes which were started by me or under my account , its a multiuser enviornment , I tried with ps -f , but it does not give me the complete answer , it gives me which shells I hv opened like tht , I want the processes like ... (4 Replies)
Discussion started by: vishsid3
4 Replies

3. Shell Programming and Scripting

how to create a ramdisk

Hi all, I wanted to make a ramdisk for a opensolaris distro. I have very little idea of how to create it? can anyone pls help me out? Is there any tutorial on creating it on the net??? Also can i make changes to the actual os itself by changing the scripts involved in ramdisk then use it to... (1 Reply)
Discussion started by: wrapster
1 Replies

4. UNIX for Dummies Questions & Answers

view others process

Hello, I hope this is an easy question. I have a few users who login through SSH and some times their bash session is using 100% cpu even though its been "idle" according to who for several days. I would like to know what command the user ran in their bash session to peg the cpu out but am... (6 Replies)
Discussion started by: taheri6
6 Replies

5. Shell Programming and Scripting

Ramdisk already defined

I am trying to mount the ramdisk for sorting, and i get the message "ramdisk already defined." What exactly is /dev/ramdisk0 and is it safe to remove it? # command sudo -S mktd 60 <<EOF initiate EOF # block of code for mktd ... && { print "ramdisk already defined." ... (1 Reply)
Discussion started by: ChicagoBlues
1 Replies

6. UNIX for Advanced & Expert Users

View process history

Hi, Is there any way to view process history. Suppose I had killed a few procs yesterday and now I want to see what were the procs that were running yesterday? (2 Replies)
Discussion started by: King Nothing
2 Replies

7. Shell Programming and Scripting

Sorting in ramdisk

Hi, I have sort command that sorts in ramdisk created by a script 'mktd' and later unmounted by script 'rmtd'. The platform is AIX. # code sudo -E mktd 44 # create ramdisk of size 44GB sort ... -k1,1 -2,2 ... # sort a file using the ramdisk on keys 1 and 2 sudo -E rmtd # unmount... (1 Reply)
Discussion started by: ChicagoBlues
1 Replies

8. UNIX for Dummies Questions & Answers

View User Mode Call Stack of Hung Process

I have a multithreaded usermode program(actually a daemon) which is in hanged state. To debug it I tried attaching the process to gdb, but the gdb hangs. gstack also gets hanged. I peeped into the proc file system and saw the process to be in sleeping state. /proc/sysrq-trigger I guess... (1 Reply)
Discussion started by: rupeshkp728
1 Replies

9. What is on Your Mind?

Moving from Desktop View to Mobile View

See attached video for a demo on how to move back and forth from the desktop view to the mobile view. Currently this only works for the home page, but I will work on some new PHP code in the future to make this work with the page we are currently on. Edit: The issue with making every page ... (2 Replies)
Discussion started by: Neo
2 Replies
xfs_logprint(8) 					      System Manager's Manual						   xfs_logprint(8)

NAME
xfs_logprint - print the log of an XFS filesystem SYNOPSIS
xfs_logprint [ options ] device DESCRIPTION
xfs_logprint prints the log of an XFS filesystem (see xfs(5)). The device argument is the pathname of the partition or logical volume con- taining the filesystem. The device can be a regular file if the -f option is used. The contents of the filesystem remain undisturbed. There are two major modes of operation in xfs_logprint. One mode is better for filesystem operation debugging. It is called the transactional view and is enabled through the -t option. The transactional view prints only the portion of the log that pertains to recovery. In other words, it prints out complete transactions between the tail and the head. This view tries to display each transaction without regard to how they are split across log records. The second mode starts printing out information from the beginning of the log. Some error blocks might print out in the beginning because the last log record usually overlaps the oldest log record. A message is printed when the physical end of the log is reached and when the logical end of the log is reached. A log record view is displayed one record at a time. Transactions that span log records may not be decoded fully. OPTIONS
-b Extract and print buffer information. Only used in transactional view. -c Attempt to continue when an error is detected. -C filename Copy the log from the filesystem to the file filename. The log itself is not printed. -d Dump the log from front to end, printing where each log record is located on disk. -D Do not decode anything; just print data. -e Exit when an error is found in the log. Normally, xfs_logprint tries to continue and unwind from bad logs. However, sometimes it just dies in bad ways. Using this option prevents core dumps. -f Specifies that the filesystem image to be processed is stored in a regular file at device (see the mkfs.xfs(8) -d file option). This might happen if an image copy of a filesystem has been made into an ordinary file with xfs_copy(8). -l logdev External log device. Only for those filesystems which use an external log. -i Extract and print inode information. Only used in transactional view. -q Extract and print quota information. Only used in transactional view. -n Do not try and interpret log data; just interpret log header information. -o Also print buffer data in hex. Normally, buffer data is just decoded, so better information can be printed. -s start-block Override any notion of where to start printing. -t Print out the transactional view. SEE ALSO
mkfs.xfs(8), mount(8). xfs_logprint(8)
All times are GMT -4. The time now is 01:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy