Sponsored Content
Full Discussion: Blockdev vs /sys/block/
Special Forums Hardware Filesystems, Disks and Memory Blockdev vs /sys/block/ Post 302905597 by vbe on Thursday 12th of June 2014 09:48:16 AM
Old 06-12-2014
Well I dont have much linux knowldge, but since you are talking disks, the same philosophy should apply:
First two give you a value of 128 (kb)
The last, blockdev since to talk like ioctl etc... and so is in blocks ( of 512 bytes) 256 block of 512 bytes...
To me then the values are much the same
This User Gave Thanks to vbe For This Post:
 

10 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

Sys Administration

What happend to the Administration board, How come no one posts there? (1 Reply)
Discussion started by: tovsky
1 Replies

2. UNIX for Dummies Questions & Answers

BSD Sys 5????

Since I failed a test that I didn't have the chance to study for, my wonderful instructor told me to write a paper about BSD sys 5. I can't find anything...does it even exist yet??? If you have any input, I would love you forever if you can enlighten me ASAP. (2 Replies)
Discussion started by: Toughgirl27
2 Replies

3. Shell Programming and Scripting

sys info script

Hi, i need a shell script that write in a file called sys.txt this: <output of date command> HN <host name> OS <OS name> <OS version> I can have this info with uname command, but I can't write these in sys.txt. Can any one help me? (1 Reply)
Discussion started by: FastMagister
1 Replies

4. Solaris

Differences Sys 5 and BSD

Hi I would like to know the difference between System V release and BSD style release. Regards, Raja (2 Replies)
Discussion started by: RajaRC
2 Replies

5. Solaris

Any sys admins from uk?

Hello Guys, im new to this forum. Im from UK and ive recently completed my SCSA I & II and also got trained in Veritas Suite (Veritas Volume Manager and Veritas Clusters, Veritas NetBackup), SAN Configuration. I was trying to get a break as a junior sun solaris admin. I am applying for the jobs... (1 Reply)
Discussion started by: megadeth
1 Replies

6. Programming

Hi errno in sys/stat.h

How should I use errno in a c program and what info does it have . I am working with directories and files. So can any one tell me How to access errno?I am using the stat() function on \etc directory and I am alble to access only the half of the directories.I am not able to access other half and... (6 Replies)
Discussion started by: vijlak
6 Replies

7. What is on Your Mind?

Network Sys Admin

Hi, my name is wesly. I an IT tech at the Junior Level. I have a bachelors degree in Computer Information Systems. I would like to fully become a Unix Sys Admin. Can anyone please tell me what I have to do. Do I have to set up a Unix or Linux server. How about Apache. Please give me clues and tips... (1 Reply)
Discussion started by: wes.lat
1 Replies

8. Solaris

Sys Admin Certification

Hi, I am planning to get certified in Solaris 10 for my own interest. Although I don't have much experience in sys admin, I have got some background in scripting and some sort of beginner level administration. But I have read in many places that one must have a good amount of experience in sys... (8 Replies)
Discussion started by: King Nothing
8 Replies

9. UNIX for Dummies Questions & Answers

need help about config. sys message.

Dear All, I am trying to config a sys mail message on solaris 10. I am doing the following commands but it dose not work with me; #touch /var/mail-test #vi /etc/syslog.cong local0.notice /var/mail-test #svcadm disable svcs:/system/system-log:default #svcadm enable... (1 Reply)
Discussion started by: ahmedamer12
1 Replies

10. Programming

Interactive Python 3.5+ sys.stdout.write() AND sys.stderr.write() bug?

(Apologies for any typos.) OSX 10.12.3 AND Windows 10. This is for the serious Python experts on at least 3.5.x and above... In script format sys.stdout.write() AND sys.stderr.write() seems to work correctly. Have I found a serious bug in the interactive sys.stdout.write() AND... (2 Replies)
Discussion started by: wisecracker
2 Replies
SYSTEMD-READAHEAD-REPLAY.SERVICE(8)			 systemd-readahead-replay.service		       SYSTEMD-READAHEAD-REPLAY.SERVICE(8)

NAME
systemd-readahead-replay.service, systemd-readahead-collect.service, systemd-readahead-done.service, systemd-readahead-done.timer, systemd- readahead - Disk read ahead logic SYNOPSIS
systemd-readahead-replay.service systemd-readahead-collect.service systemd-readahead-done.service systemd-readahead-done.timer /usr/lib/systemd/systemd-readahead/systemd-readahead [OPTIONS...] COMMAND [DIRECTORY | FILE] DESCRIPTION
systemd-readahead-collect.service is a service that collects disk usage patterns at boot time. systemd-readahead-replay.service is a service that replays this access data collected at the subsequent boot. Since disks tend to be magnitudes slower than RAM, this is intended to improve boot speeds by pre-loading early at boot all data on disk that is known to be read for the complete boot process. systemd-readahead-done.service is executed a short while after boot completed and signals systemd-readahead-collect.service to end data collection. On this signal, this service will then sort the collected disk accesses and store information about them in /.readahead. Normally, both systemd-readahead-collect.service and systemd-readahead-replay.service are activated at boot so that access patterns from the preceding boot are replayed and new data collected for the subsequent boot. However, on read-only media where the collected data cannot be stored, it might be a good idea to disable systemd-readahead-collect.service. On rotating media, when replaying disk accesses at early boot, systemd-readahead-replay.service will order read requests by their location on disk. On non-rotating media, they will be ordered by their original access timestamp. If the file system supports it, systemd-readahead-collect.service will also defragment and rearrange files on disk to optimize subsequent boot times. OPTIONS
systemd-readahead understands the following options: -h, --help Prints a short help text and exits. --max-files= Maximum number of files to read ahead. Only valid for thes collect command. --file-size-max= Maximum size of files in bytes to read ahead. Only valid for the collect and replay commands. --timeout= Maximum time in microseconds to spend collecting data. Only valid for the collect command. COMMANDS
The following commands are understood by systemd-readahead: collect [DIRECTORY] Collect read-ahead data on early boot. When terminating, it will write out a pack file to the indicated directory containing the read-ahead data. replay [DIRECTORY] Perform read-ahead on the specified directory tree. analyze [FILE] Dumps the content of the read-ahead pack file to the terminal. For each file, the output lists approximately how much will be read ahead by the replay command. SEE ALSO
systemd(1) systemd 208 SYSTEMD-READAHEAD-REPLAY.SERVICE(8)
All times are GMT -4. The time now is 10:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy