How can gdb be used to find out why this command fails ? [/dev/sdb]
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
# partition format details
##########################
# fsck.reiser4 --build-fs --force /dev/sdb
Fscking the /dev/sdb block device.
***** fsck.reiser4 started at Thu Mar 5 16:54:06 2015
Reiser4 fs was detected on /dev/sdb.
Master super block (16):
magic: ReIsEr4
blksize: 4096
format: 0x0 (format40)
uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede
label: <none>
Format super block (17):
plugin: format40
description: Disk-format plugin.
version: 0
magic: ReIsEr40FoRmAt
mkfs id: 0x1ddaf754
flushes: 0
blocks: 488378640
free blocks: 217146980
root block: 37017218
tail policy: 0x2 (smart)
next oid: 0xedade
file count: 188313
tree height: 6
key policy: LARGE
You would normally use it if you had source code compiled with symbols so that you could debug a program.
Odds are that you do not have the source for mount readily available, however it is very possible to obtain that source, rebuild it with symbols, and then perform some debug.
HOWEVER, you do not need to go to that level to diagnose this issue. You just need to figure out how to use the mount command. Veerain is on the way to helping you with that. Basically you need to determine the type of disk partition which you are attempting to mount and then tailor the arguments for the mount command to perform the operation. You also need to get the syntax for mount correctly as well and need to be root or sudo, which you already appear to be.
So for now just realize that GDB is not a general debugger for system commands and it's really a debugger for source code debugging. It is very powerful, just not the tool which will benefit you in this particular case.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.