Internal error xfs_sb_read_verify at line 726
Subsystems (2)
Today I accidentally tried to mount my backup disk at /dev/sdc instead of /dev/sdc1 and this is what happened:
...
EXT4-fs (sdc): VFS: Can't find ext4 filesystem
FAT-fs (sdc): bogus number of reserved sectors
FAT-fs (sdc): Can't find a valid FAT filesystem
FAT-fs (sdc): bogus number of reserved sectors
FAT-fs (sdc): Can't find a valid FAT filesystem
ISOFS: Unable to identify CD-ROM format.
XFS (sdc): bad magic numberffff8800db620000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
XFS (sdc): Internal error xfs_sb_read_verify at line 726 of file fs/xfs/xfs_mount.c. Caller 0xffffffff8119e5cd
CPU: 3 PID: 68 Comm: kworker/3:1H Not tainted 3.9.0-10518-gd7ab730-dirty #440 Hardware name: System manufacturer System Product Name/M4A78T-E, BIOS 3503 04/13/2011 Workqueue: xfslogd xfs_buf_iodone_work ffffffff81537e9c ffffffff811a0416 000002d600000000 ffffffff8119e5cd ffff8800db2e7500 0000000000000016 ffff8801c0242800 ffff88021fd94f00 ffffffff811e93d5 ffffffff8119e5cd ffff8802168ed820 ffff8800db2e75a0 Call Trace: [<ffffffff81537e9c>] ? dump_stack+0xc/0x15 [<ffffffff811a0416>] ? xfs_corruption_error+0x56/0x80 [<ffffffff8119e5cd>] ? xfs_buf_iodone_work+0x6d/0xa0 [<ffffffff811e93d5>] ? xfs_sb_read_verify+0xf5/0x120 [<ffffffff8119e5cd>] ? xfs_buf_iodone_work+0x6d/0xa0 [<ffffffff8119e5cd>] ? xfs_buf_iodone_work+0x6d/0xa0 [<ffffffff81072cbc>] ? process_one_work+0x13c/0x3c0 [<ffffffff8107304d>] ? worker_thread+0x10d/0x3a0 [<ffffffff81072f40>] ? process_one_work+0x3c0/0x3c0 [<ffffffff8107912f>] ? kthread+0xaf/0xc0 [<ffffffff81079080>] ? __kthread_parkme+0x80/0x80 [<ffffffff8153cf2c>] ? ret_from_fork+0x7c/0xb0 [<ffffffff81079080>] ? __kthread_parkme+0x80/0x80
XFS (sdc): Corruption detected. Unmount and run xfs_repair XFS (sdc): SB validate failed with error 22.
XFS (sdc1): Mounting Filesystem
XFS (sdc1): Ending clean mount
Seems a bit overkill to me ;-).
Signature · 6 lines
Markus _______________________________________________ xfs mailing list [email protected] http://oss.sgi.com/mailman/listinfo/xfs
Quoted 16 lines · Markus Trippelsdorf
Today I accidentally tried to mount my backup disk at
/dev/sdcinstead of/dev/sdc1and this is what happened:...
EXT4-fs (sdc): VFS: Can't find ext4 filesystem
FAT-fs (sdc): bogus number of reserved sectors
FAT-fs (sdc): Can't find a valid FAT filesystem
FAT-fs (sdc): bogus number of reserved sectors
FAT-fs (sdc): Can't find a valid FAT filesystem
ISOFS: Unable to identify CD-ROM format.
XFS (sdc): bad magic numberffff8800db620000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
XFS (sdc): Internal errorxfs_sb_read_verifyat line 726 of filefs/xfs/xfs_mount.c. Caller0xffffffff8119e5cd
This seems to be a recent regression.
Comments above xfs_sb_quiet_read_verify() indicate that this behavior is to be avoided:
* We may be probed for a filesystem match, so we may not want to emit
* messages when the superblock buffer is not actually an XFS superblock.
and it checks for proper magic prior to all the chattiness above int that function.
The superblock read is suposed to choose whether to be noisy or not, in xfs_readsb():
reread:
bp = xfs_buf_read_uncached(mp->m_ddev_targp, XFS_SB_DADDR,
BTOBB(sector_size), 0,
loud ? &xfs_sb_buf_ops
: &xfs_sb_quiet_buf_ops);so it looks like this *should* be working properly.
I'll look into it and send a patch in a a bit.
(FWIW though, I don't get this probing from the kernel; I only see it if I specify a -t xfs type on the mount command)
Thanks,
-Eric
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 23 lines · Eric Sandeen
Quoted 16 lines · Markus Trippelsdorf
Today I accidentally tried to mount my backup disk at
/dev/sdcinstead of/dev/sdc1and this is what happened:...
EXT4-fs (sdc): VFS: Can't find ext4 filesystem
FAT-fs (sdc): bogus number of reserved sectors
FAT-fs (sdc): Can't find a valid FAT filesystem
FAT-fs (sdc): bogus number of reserved sectors
FAT-fs (sdc): Can't find a valid FAT filesystem
ISOFS: Unable to identify CD-ROM format.
XFS (sdc): bad magic numberffff8800db620000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
XFS (sdc): Internal errorxfs_sb_read_verifyat line 726 of filefs/xfs/xfs_mount.c. Caller0xffffffff8119e5cdThis seems to be a recent regression.
Comments above
xfs_sb_quiet_read_verify()indicate that this behavior is to be avoided:
Quoted 9 lines
* We may be probed for a filesystem match, so we may not want to emit
* messages when the superblock buffer is not actually an XFS superblock.and it checks for proper magic prior to all the chattiness above int that function.
The superblock read is suposed to choose whether to be noisy or not, in
xfs_readsb():
The following patch fixes the issue for me:
fs/xfs/xfs_mount.c +5 -0
@@ -721,6 +721,11 @@ xfs_sb_read_verify( } error =xfs_sb_verify (bp); +if (error ==XFS_ERROR (EWRONGFS )) { +xfs_buf_ioerror (bp,EWRONGFS ); +return ; + } + out_error:if (error) {XFS_CORRUPTION_ERROR (__func__,XFS_ERRLEVEL_LOW , mp, bp->b_addr);
Signature · 6 lines
Markus _______________________________________________ xfs mailing list [email protected] http://oss.sgi.com/mailman/listinfo/xfs
Quoted 43 lines · Markus Trippelsdorf
Quoted 23 lines · Eric Sandeen
Quoted 16 lines · Markus Trippelsdorf
Today I accidentally tried to mount my backup disk at
/dev/sdcinstead of/dev/sdc1and this is what happened:...
EXT4-fs (sdc): VFS: Can't find ext4 filesystem
FAT-fs (sdc): bogus number of reserved sectors
FAT-fs (sdc): Can't find a valid FAT filesystem
FAT-fs (sdc): bogus number of reserved sectors
FAT-fs (sdc): Can't find a valid FAT filesystem
ISOFS: Unable to identify CD-ROM format.
XFS (sdc): bad magic numberffff8800db620000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
XFS (sdc): Internal errorxfs_sb_read_verifyat line 726 of filefs/xfs/xfs_mount.c. Caller0xffffffff8119e5cdThis seems to be a recent regression.
Comments above
xfs_sb_quiet_read_verify()indicate that this behavior is to be avoided:Quoted 9 lines
* We may be probed for a filesystem match, so we may not want to emit
* messages when the superblock buffer is not actually an XFS superblock.and it checks for proper magic prior to all the chattiness above int that function.
The superblock read is suposed to choose whether to be noisy or not, in
xfs_readsb():The following patch fixes the issue for me:
fs/xfs/xfs_mount.c +0
-0@@ -721,6 +721,11 @@ xfs_sb_read_verify( }
fs/xfs/xfs_mount.c xfs_sb_read_verify( · line 731
Quoted 10 lines
fs/xfs/xfs_mount.c +5
-0error =xfs_sb_verify (bp); +if (error ==XFS_ERROR (EWRONGFS )) { +xfs_buf_ioerror (bp,EWRONGFS ); +return ; + } + out_error:if (error) {XFS_CORRUPTION_ERROR (__func__,XFS_ERRLEVEL_LOW , mp, bp->b_addr);
That might make sense, I don't think we need the loudness for EWRONGFS no matter how we got there.
But:
Out of curiosity, what was the actual mount command you used? It seems like the auto-probing should have set the MS_SILENT flag to avoid this in the first place, i.e. we should have gone down the quiet path (xfs_sb_quiet_read_verify) and avoided this altogether.
How do you reproduce this?
If I were to patch xfs_read_sb_verify, I'd probably do it like this:
fs/xfs/xfs_mount.c +3 -1
@@ -723,7 +723,9 @@ xfs_sb_read_verify( out_error:if (error) { -XFS_CORRUPTION_ERROR (__func__,XFS_ERRLEVEL_LOW , mp, bp->b_addr); +if (error !=EWRONGFS ) +XFS_CORRUPTION_ERROR (__func__,XFS_ERRLEVEL_LOW , + mp, bp->b_addr);xfs_buf_ioerror (bp, error); } }
Because it keeps a single return point in the function, and . . .
XFS_ERROR() is never used on the right side of a test; it's only to turn an error return into a BUG_ON for certain error numbers when they're set; i.e. it'd fire in xfs_mount_validate_sb before we ever got to the caller:
xfs_warn(mp, "bad magic number");
return XFS_ERROR(EWRONGFS); /* would BUG if configured to do so */
Thanks,
-Eric
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 58 lines · Eric Sandeen
Quoted 43 lines · Markus Trippelsdorf
Quoted 23 lines · Eric Sandeen
Quoted 16 lines · Markus Trippelsdorf
Today I accidentally tried to mount my backup disk at
/dev/sdcinstead of/dev/sdc1and this is what happened:...
EXT4-fs (sdc): VFS: Can't find ext4 filesystem
FAT-fs (sdc): bogus number of reserved sectors
FAT-fs (sdc): Can't find a valid FAT filesystem
FAT-fs (sdc): bogus number of reserved sectors
FAT-fs (sdc): Can't find a valid FAT filesystem
ISOFS: Unable to identify CD-ROM format.
XFS (sdc): bad magic numberffff8800db620000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
XFS (sdc): Internal errorxfs_sb_read_verifyat line 726 of filefs/xfs/xfs_mount.c. Caller0xffffffff8119e5cdThis seems to be a recent regression.
Comments above
xfs_sb_quiet_read_verify()indicate that this behavior is to be avoided:Quoted 9 lines
* We may be probed for a filesystem match, so we may not want to emit
* messages when the superblock buffer is not actually an XFS superblock.and it checks for proper magic prior to all the chattiness above int that function.
The superblock read is suposed to choose whether to be noisy or not, in
xfs_readsb():The following patch fixes the issue for me:
fs/xfs/xfs_mount.c +0
-0@@ -721,6 +721,11 @@ xfs_sb_read_verify( }fs/xfs/xfs_mount.c xfs_sb_read_verify( · line 731
Quoted 10 lines
fs/xfs/xfs_mount.c +5
-0error =xfs_sb_verify (bp); +if (error ==XFS_ERROR (EWRONGFS )) { +xfs_buf_ioerror (bp,EWRONGFS ); +return ; + } + out_error:if (error) {XFS_CORRUPTION_ERROR (__func__,XFS_ERRLEVEL_LOW , mp, bp->b_addr);That might make sense, I don't think we need the loudness for EWRONGFS no matter how we got there.
Quoted 8 lines
But:
Out of curiosity, what was the actual mount command you used? It seems like the auto-probing should have set the
MS_SILENTflag to avoid this in the first place, i.e. we should have gone down the quiet path (xfs_sb_quiet_read_verify) and avoided this altogether.How do you reproduce this?
I power on the drive and simply run:
# mount /dev/sdc /mnt
Quoted 18 lines
If I were to patch
xfs_read_sb_verify, I'd probably do it like this:fs/xfs/xfs_mount.c +3
-1@@ -723,7 +723,9 @@ xfs_sb_read_verify( out_error:if (error) { -XFS_CORRUPTION_ERROR (__func__,XFS_ERRLEVEL_LOW , mp, bp->b_addr); +if (error !=EWRONGFS ) +XFS_CORRUPTION_ERROR (__func__,XFS_ERRLEVEL_LOW , + mp, bp->b_addr);xfs_buf_ioerror (bp, error); } }
Quoted 4 lines
Because it keeps a single return point in the function, and . . .
XFS_ERROR()is never used on the right side of a test; it's only to turn an error return into aBUG_ONfor certain error numbers when they're set;
OK, makes sense. Thanks.
I like your patch better, so lets use it.
Signature · 6 lines
Markus _______________________________________________ xfs mailing list [email protected] http://oss.sgi.com/mailman/listinfo/xfs
Quoted 66 lines · Markus Trippelsdorf
Quoted 65 lines · Eric Sandeen
Quoted 43 lines · Markus Trippelsdorf
Quoted 23 lines · Eric Sandeen
Quoted 16 lines · Markus Trippelsdorf
Today I accidentally tried to mount my backup disk at
/dev/sdcinstead of/dev/sdc1and this is what happened:...
EXT4-fs (sdc): VFS: Can't find ext4 filesystem
FAT-fs (sdc): bogus number of reserved sectors
FAT-fs (sdc): Can't find a valid FAT filesystem
FAT-fs (sdc): bogus number of reserved sectors
FAT-fs (sdc): Can't find a valid FAT filesystem
ISOFS: Unable to identify CD-ROM format.
XFS (sdc): bad magic numberffff8800db620000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
XFS (sdc): Internal errorxfs_sb_read_verifyat line 726 of filefs/xfs/xfs_mount.c. Caller0xffffffff8119e5cdThis seems to be a recent regression.
Comments above
xfs_sb_quiet_read_verify()indicate that this behavior is to be avoided:Quoted 9 lines
* We may be probed for a filesystem match, so we may not want to emit
* messages when the superblock buffer is not actually an XFS superblock.and it checks for proper magic prior to all the chattiness above int that function.
The superblock read is suposed to choose whether to be noisy or not, in
xfs_readsb():The following patch fixes the issue for me:
fs/xfs/xfs_mount.c +0
-0@@ -721,6 +721,11 @@ xfs_sb_read_verify( }fs/xfs/xfs_mount.c xfs_sb_read_verify( · line 731
Quoted 10 lines
fs/xfs/xfs_mount.c +5
-0error =xfs_sb_verify (bp); +if (error ==XFS_ERROR (EWRONGFS )) { +xfs_buf_ioerror (bp,EWRONGFS ); +return ; + } + out_error:if (error) {XFS_CORRUPTION_ERROR (__func__,XFS_ERRLEVEL_LOW , mp, bp->b_addr);That might make sense, I don't think we need the loudness for EWRONGFS no matter how we got there.
But:
Out of curiosity, what was the actual mount command you used? It seems like the auto-probing should have set the
MS_SILENTflag to avoid this in the first place, i.e. we should have gone down the quiet path (xfs_sb_quiet_read_verify) and avoided this altogether.
Quoted 5 lines
Quoted 1 line
How do you reproduce this?
I power on the drive and simply run:
# mount /dev/sdc /mnt
Interesting. On my test box, that never even issues the mount syscall, because it uses blkid (I guess) to probe, and finds nothing.
Which util-linux do you have?
An strace -v of the mount command might be useful.
-Eric
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 69 lines · Eric Sandeen
Quoted 68 lines · Markus Trippelsdorf
Quoted 66 lines · Eric Sandeen
Quoted 43 lines · Markus Trippelsdorf
Quoted 23 lines · Eric Sandeen
Quoted 16 lines · Markus Trippelsdorf
Today I accidentally tried to mount my backup disk at
/dev/sdcinstead of/dev/sdc1and this is what happened:...
EXT4-fs (sdc): VFS: Can't find ext4 filesystem
FAT-fs (sdc): bogus number of reserved sectors
FAT-fs (sdc): Can't find a valid FAT filesystem
FAT-fs (sdc): bogus number of reserved sectors
FAT-fs (sdc): Can't find a valid FAT filesystem
ISOFS: Unable to identify CD-ROM format.
XFS (sdc): bad magic numberffff8800db620000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
XFS (sdc): Internal errorxfs_sb_read_verifyat line 726 of filefs/xfs/xfs_mount.c. Caller0xffffffff8119e5cdThis seems to be a recent regression.
Comments above
xfs_sb_quiet_read_verify()indicate that this behavior is to be avoided:Quoted 9 lines
* We may be probed for a filesystem match, so we may not want to emit
* messages when the superblock buffer is not actually an XFS superblock.and it checks for proper magic prior to all the chattiness above int that function.
The superblock read is suposed to choose whether to be noisy or not, in
xfs_readsb():The following patch fixes the issue for me:
fs/xfs/xfs_mount.c +0
-0@@ -721,6 +721,11 @@ xfs_sb_read_verify( }fs/xfs/xfs_mount.c xfs_sb_read_verify( · line 731
Quoted 10 lines
fs/xfs/xfs_mount.c +5
-0error =xfs_sb_verify (bp); +if (error ==XFS_ERROR (EWRONGFS )) { +xfs_buf_ioerror (bp,EWRONGFS ); +return ; + } + out_error:if (error) {XFS_CORRUPTION_ERROR (__func__,XFS_ERRLEVEL_LOW , mp, bp->b_addr);That might make sense, I don't think we need the loudness for EWRONGFS no matter how we got there.
But:
Out of curiosity, what was the actual mount command you used? It seems like the auto-probing should have set the
MS_SILENTflag to avoid this in the first place, i.e. we should have gone down the quiet path (xfs_sb_quiet_read_verify) and avoided this altogether.How do you reproduce this?
Quoted 8 lines
Quoted 3 lines
I power on the drive and simply run:
# mount /dev/sdc /mntInteresting. On my test box, that never even issues the mount syscall, because it uses blkid (I guess) to probe, and finds nothing.
Which util-linux do you have?
v2.21.2
Quoted 1 line
An strace -v of the mount command might be useful.
execve("/bin/mount", ["mount", "/dev/sdc", "/mnt"], [/* 44 vars */]) = 0
brk(0) = 0x1ddc000mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f3f5a3a5000access("/etc/ld.so.preload", R_OK) = 0open("/etc/ld.so.preload", O_RDONLY|O_CLOEXEC) = 3fstat(3, {st_mode=S_IFREG|0644, st_size=23, ...}) = 0mmap(NULL, 23, PROT_READ|PROT_WRITE, MAP_PRIVATE, 3, 0) = 0x7f3f5a3a4000
close(3) = 0open("/usr/lib/libamdlibm.so", O_RDONLY|O_CLOEXEC) = 3read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0@\245\0\0\0\0\0\0"..., 832) = 832fstat(3, {st_mode=S_IFREG|0644, st_size=699125, ...}) = 0mmap(NULL, 2741432, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f3f59ee9000 mprotect(0x7f3f59f40000, 2097152, PROT_NONE) = 0mmap(0x7f3f5a140000, 286720, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x57000) = 0x7f3f5a140000 mmap(0x7f3f5a186000, 1208, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3f5a186000
close(3) = 0munmap(0x7f3f5a3a4000, 23) = 0open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3fstat(3, {st_mode=S_IFREG|0644, st_size=139673, ...}) = 0mmap(NULL, 139673, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f3f5a382000
close(3) = 0open("/lib/libblkid.so.1", O_RDONLY|O_CLOEXEC) = 3read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 832) = 832fstat(3, {st_mode=S_IFREG|0755, st_size=155512, ...}) = 0mmap(NULL, 157484, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f3f5a35b000 mmap(0x7f3f5a37e000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x22000) = 0x7f3f5a37e000
close(3) = 0open("/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = 3read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\200\33\2\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=9693409, ...}) = 0mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f3f5a35a000 mmap(NULL, 3594688, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f3f59b7b000 mprotect(0x7f3f59ce0000, 2093056, PROT_NONE) = 0
mmap(0x7f3f59edf000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x164000) = 0x7f3f59edf000 mmap(0x7f3f59ee5000, 14784, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3f59ee5000
close(3) = 0open("/lib/libuuid.so.1", O_RDONLY|O_CLOEXEC) = 3read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=16272, ...}) = 0mmap(NULL, 18236, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f3f5a355000 mmap(0x7f3f5a359000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0x7f3f5a359000
close(3) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f3f5a354000
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f3f5a352000
arch_prctl(ARCH_SET_FS, 0x7f3f5a352780) = 0
mprotect(0x7f3f59edf000, 16384, PROT_READ) = 0
mprotect(0x7f3f5a3a6000, 4096, PROT_READ) = 0
munmap(0x7f3f5a382000, 139673) = 0
brk(0) = 0x1ddc000
brk(0x1dfd000) = 0x1dfd000
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=1534640, ...}) = 0
mmap(NULL, 1534640, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f3f5a1db000
close(3) = 0
umask(022) = 022
open("/dev/null", O_RDWR) = 3
close(3) = 0
getuid() = 0
geteuid() = 0stat("/dev/sdc", {st_mode=S_IFBLK|0660, st_rdev=makedev(8, 32), ...}) = 0 readlink("/dev", 0x7fff283f5920, 4096) = -1 EINVAL (Invalid argument) readlink("/dev/sdc", 0x7fff283f5920, 4096) = -1 EINVAL (Invalid argument) stat("/dev/sdc", {st_mode=S_IFBLK|0660, st_rdev=makedev(8, 32), ...}) = 0 rt_sigprocmask(SIG_BLOCK, ~[TRAP SEGV RTMIN RT_1], NULL, 8) = 0open("/dev/sdc", O_RDONLY) = 3fadvise64(3, 0, 0, POSIX_FADV_RANDOM) = 0fstat(3, {st_mode=S_IFBLK|0660, st_rdev=makedev(8, 32), ...}) = 0
uname({sys="Linux", node="x4", ...}) = 0
ioctl(3, BLKGETSIZE64, 1000204886016) = 0
open("/sys/dev/block/8:32", O_RDONLY) = 4newfstatat(4, "partition", 0x7fff283f6490, 0) = -1 ENOENT (No such file or directory)openat(4, "dm/uuid", O_RDONLY) = -1 ENOENT (No such file or directory)
close(4) = 0ioctl(3, CDROM_GET_CAPABILITY or SNDRV_SEQ_IOCTL_UNSUBSCRIBE_PORT, 0) = -1 ENOTTY (Inappropriate ioctl for device)lseek(3, 1000204795904, SEEK_SET) = 1000204795904read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 64) = 64lseek(3, 1000204877824, SEEK_SET) = 1000204877824read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 256) = 256lseek(3, 0, SEEK_SET) = 0read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 256) = 256lseek(3, 4096, SEEK_SET) = 4096read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 256) = 256lseek(3, 1000204885504, SEEK_SET) = 1000204885504read(3, "EFI PART\0\0\1\0\\\0\0\0\253 \1;\0\0\0\0\257mpt\0\0\0\0"..., 512) = 512lseek(3, 1000204754432, SEEK_SET) = 1000204754432read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 512) = 512lseek(3, 1000204884992, SEEK_SET) = 1000204884992read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 48) = 48lseek(3, 1000204853760, SEEK_SET) = 1000204853760read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 24) = 24lseek(3, 1000204755456, SEEK_SET) = 1000204755456read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 24) = 24lseek(3, 1000204754944, SEEK_SET) = 1000204754944read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 24) = 24lseek(3, 1000204681728, SEEK_SET) = 1000204681728read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 24) = 24
lseek(3, 1000204880384, SEEK_SET) = 1000204880384 read(3, "\0\0\0\0", 4) = 4 lseek(3, 4096, SEEK_SET) = 4096
read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1024) = 1024lseek(3, 1000204881920, SEEK_SET) = 1000204881920read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 4096lseek(3, 0, SEEK_SET) = 0read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1024) = 1024lseek(3, 1024, SEEK_SET) = 1024read(3, "\257=\306\17\203\204rG\216y=i\330G}\344\341Fx\2110\211\5E\211s\250\262\335\221A\370"..., 1024) = 1024lseek(3, 1048576, SEEK_SET) = 1048576read(3, "XFSB\0\0\20\0\0\0\0\0\16\216\f\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1024) = 1024lseek(3, 3072, SEEK_SET) = 3072read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1024) = 1024lseek(3, 7168, SEEK_SET) = 7168read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1024) = 1024lseek(3, 15360, SEEK_SET) = 15360read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1024) = 1024lseek(3, 31744, SEEK_SET) = 31744read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1024) = 1024lseek(3, 64512, SEEK_SET) = 64512read(3, "\0\0\0\0\30\1\r\25\3dir\30\0\16\0\0\0\0\0\30\1\r\26\7dirname"..., 1024) = 1024lseek(3, 8192, SEEK_SET) = 8192read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1024) = 1024lseek(3, 65536, SEEK_SET) = 65536read(3, "IN\200\0\2\2\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0"..., 1024) = 1024lseek(3, 32768, SEEK_SET) = 32768read(3, "XAGF\0\0\0\1\0\0\0\0\0c\320\231\0\0\22\321\0\0 \353\0\0\0\0\0\0\0\2"..., 1024) = 1024lseek(3, 131072, SEEK_SET) = 131072read(3, "\0\0\0\0\0\v\311'\25%gconf-tree-zh_CN.xml\2\0"..., 41) = 41lseek(3, 135168, SEEK_SET) = 135168
read(3, ".schema\31H\213\205(\377\377\1\360\377\377\0(\0\0\1\331\27.dyngro"..., 41) = 41lseek(3, 139264, SEEK_SET) = 139264read(3, "INA\300\2\1\0\0\0\0\3\350\0\0\3\350\0\0\0\3\0\0\0\0\0\0\0\0\0\0\0M"..., 41) = 41lseek(3, 143360, SEEK_SET) = 143360read(3, "IN\241\377\2\1\0\0\0\0\0\0\0\0\0\0\0\0\0\16\0\0\0\0\0\0\0\0\0\0\0006"..., 41) = 41lseek(3, 147456, SEEK_SET) = 147456read(3, "IN\201\244\2\2\0\0\0\0\0\0\0\0\0\0\0\0\0\16\0\0\0\0\0\0\0\0\0\0\0@"..., 41) = 41lseek(3, 151552, SEEK_SET) = 151552read(3, "INA\355\2\1\0\0\0\0\0\0\0\0\0\0\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0i"..., 41) = 41lseek(3, 155648, SEEK_SET) = 155648read(3, "INA\355\2\1\0\0\0\0\0\0\0\0\0\0\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0P"..., 41) = 41lseek(3, 159744, SEEK_SET) = 159744read(3, "INA\355\2\1\0\0\0\0\3\350\0\0\3\350\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0U"..., 41) = 41lseek(3, 163840, SEEK_SET) = 163840read(3, "INA\355\2\2\0\0\0\0\3\350\0\0\0d\0\0\0\4\0\0\0\0\0\0\0\0\0\0\0\36"..., 41) = 41lseek(3, 167936, SEEK_SET) = 167936read(3, "INA\355\2\1\0\0\0\0\3\350\0\0\3\350\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\32"..., 41) = 41lseek(3, 172032, SEEK_SET) = 172032read(3, "INA\355\2\1\0\0\0\0\3\350\0\0\3\350\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\31"..., 41) = 41lseek(3, 176128, SEEK_SET) = 176128read(3, "INA\355\2\1\0\0\0\0\3\350\0\0\0d\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\31"..., 41) = 41lseek(3, 180224, SEEK_SET) = 180224read(3, "IN\201\244\2\2\0\0\0\0\3\350\0\0\3\350\0\0\0\16\0\0\0\0\0\0\0\0\0\0\0\34"..., 41) = 41lseek(3, 184320, SEEK_SET) = 184320read(3, "INA\350\2\1\0\0\0\0\0\0\0\0\0#\0\0\0\3\0\0\0\0\0\0\0\0\0\0\0M"..., 41) = 41lseek(3, 188416, SEEK_SET) = 188416read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 41) = 41lseek(3, 192512, SEEK_SET) = 192512read(3, "CI\201\244\2\2\1\330\377\377\rX\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\2"..., 41) = 41lseek(3, 196608, SEEK_SET) = 196608read(3, "\0\0\0\0\10\265\355\233\10patterns\0\0\0\0\0\2\0\0\0\0\0\20\245u\243"..., 41) = 41lseek(3, 200704, SEEK_SET) = 200704read(3, "IN\201\244\2\2\0\0\0\0\0\0\0\0\0\0\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0008"..., 41) = 41lseek(3, 204800, SEEK_SET) = 204800read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 41) = 41lseek(3, 208896, SEEK_SET) = 208896read(3, "radient-select-next\")\n (m"..., 41) = 41lseek(3, 212992, SEEK_SET) = 212992read(3, " KDE4WorkspaceConfigVersion.cmak"..., 41) = 41lseek(3, 217088, SEEK_SET) = 217088read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 41) = 41lseek(3, 221184, SEEK_SET) = 221184read(3, "\0\0\0\0\1%\24\245\23libvex_trc_values.h\0\0\2\0"..., 41) = 41lseek(3, 225280, SEEK_SET) = 225280read(3, ";\n template <\n typenam"..., 41) = 41lseek(3, 229376, SEEK_SET) = 229376read(3, "\0\0\0\0\30S\17\201\5omp.h\2\0\0\0\0\0\30S\17\202\vpmmintr"..., 41) = 41lseek(3, 233472, SEEK_SET) = 233472read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 41) = 41lseek(3, 237568, SEEK_SET) = 237568
read(3, "`Q\371\364\315\242\307T\254W\234*\342\225\3745s\224\330N\256\227\361\335\314ow\352;\33w\346"..., 41) = 41lseek(3, 241664, SEEK_SET) = 241664
read(3, "\246\250\355\371\203Z\357\240\thgz\24bbS3A(=@\251\221S\6\\\316\346P\246\312\375"..., 41) = 41lseek(3, 245760, SEEK_SET) = 245760read(3, "\265P\212\3574F\4\31\1\202!\4\7\222\205\204\345\r\237\211\t\37\365\360)\0<\274\362\273z\320"..., 41) = 41lseek(3, 249856, SEEK_SET) = 249856
read(3, "sPPC.def\300\270\252\333\0\210\1\360\377\377\0(\0\1\30\202\27.Builti"..., 41) = 41lseek(3, 253952, SEEK_SET) = 253952read(3, "bleCode.h.O9fYB4\0\0\0\0\0\0\1\360\0\0\0\0\0\1\27\257"..., 41) = 41lseek(3, 258048, SEEK_SET) = 258048read(3, "ON_GENTOO \"/usr/bin/kconfig_comp"..., 41) = 41lseek(3, 393216, SEEK_SET) = 393216read(3, "\0\0\0\0\3\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\3\0\2\0\0\0\0\0\0\0\0\0"..., 41) = 41lseek(3, 397312, SEEK_SET) = 397312
read(3, "\0\0\0\201\376\0\0\200\177w3\213T$\20\211\327\201\347\377\377\377\177\201\377\0\0\200\177w\0371"..., 41) = 41lseek(3, 401408, SEEK_SET) = 401408read(3, "\n\n- Complex representations of i"..., 41) = 41lseek(3, 405504, SEEK_SET) = 405504read(3, "taglib\n\n*acoustid-fingerprinter-"..., 41) = 41lseek(3, 409600, SEEK_SET) = 409600read(3, " content=\"cluster software, Inte"..., 41) = 41lseek(3, 413696, SEEK_SET) = 413696read(3, "sqlite\1\360\0\0\0\0\20[J\345\tsecmod.db\0\0\0\0\2\10"..., 41) = 41lseek(3, 417792, SEEK_SET) = 417792read(3, "\0\35\324E\0\0\0\5\0\35\324d\0\0\0\5\0\35\341o\0\0\0\5\0\35\341\204\0\0\0\5"..., 41) = 41lseek(3, 421888, SEEK_SET) = 421888read(3, "\10tgmath.h\0\0\0\0\0\0000\0\0\0\0\30 \r\223\vtmmintr"..., 41) = 41lseek(3, 425984, SEEK_SET) = 425984read(3, " coder module is defined in this"..., 41) = 41lseek(3, 430080, SEEK_SET) = 430080read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 41) = 41lseek(3, 434176, SEEK_SET) = 434176read(3, "ollowing disclaimer in the\n * "..., 41) = 41lseek(3, 438272, SEEK_SET) = 438272read(3, "he implied warranty of\n MERCHA"..., 41) = 41lseek(3, 442368, SEEK_SET) = 442368read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 41) = 41lseek(3, 446464, SEEK_SET) = 446464read(3, "r and have the text on the same "..., 41) = 41lseek(3, 450560, SEEK_SET) = 450560read(3, "rs are strongly encouraged to\nco"..., 41) = 41lseek(3, 454656, SEEK_SET) = 454656read(3, "he @code{gfc_error_flag_test} fu"..., 41) = 41lseek(3, 458752, SEEK_SET) = 458752read(3, "amp{==|} and\n@samp{--|} mean @co"..., 41) = 41lseek(3, 462848, SEEK_SET) = 462848read(3, "sed to variables), at the very b"..., 41) = 41lseek(3, 466944, SEEK_SET) = 466944read(3, "structor} member.\n\n\n@subsection "..., 41) = 41lseek(3, 471040, SEEK_SET) = 471040
read(3, "-------\n\nFor specific bindings ("..., 41) = 41lseek(3, 475136, SEEK_SET) = 475136read(3, "de{tb_uop_root}\nsymtree exactly "..., 41) = 41lseek(3, 479232, SEEK_SET) = 479232read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 41) = 41lseek(3, 483328, SEEK_SET) = 483328read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 41) = 41lseek(3, 487424, SEEK_SET) = 487424read(3, "ta:\t0\nUndoDepth:\t12\nUpdateFlex:\t"..., 41) = 41lseek(3, 491520, SEEK_SET) = 491520read(3, "mma_q\n#include <boost/math/speci"..., 41) = 41lseek(3, 495616, SEEK_SET) = 495616read(3, "shing in size\n // fas"..., 41) = 41lseek(3, 499712, SEEK_SET) = 499712read(3, "the largest term in the\n "..., 41) = 41lseek(3, 503808, SEEK_SET) = 503808read(3, " template <class RealType,"..., 41) = 41lseek(3, 507904, SEEK_SET) = 507904read(3, ",\n &r,\n "..., 41) = 41lseek(3, 512000, SEEK_SET) = 512000read(3, " inline RealType find_degre"..., 41) = 41lseek(3, 516096, SEEK_SET) = 516096read(3, " is %1%\", result, Policy());\n "..., 41) = 41lseek(3, 520192, SEEK_SET) = 520192read(3, "tion);\n }\n templ"..., 41) = 41lseek(3, 0, SEEK_SET) = 0read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1377) = 1377lseek(3, 8192, SEEK_SET) = 8192read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1377) = 1377lseek(3, 65536, SEEK_SET) = 65536read(3, "IN\200\0\2\2\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0"..., 1377) = 1377lseek(3, 262144, SEEK_SET) = 262144read(3, "\0\1\251M\0\0\0&\0\1\251x\0\0\0\"\0\1\251\234\0\0\0\1\0\1\251\366\0\0\0\10"..., 1377) = 1377lseek(3, 9728, SEEK_SET) = 9728read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 512) = 512lseek(3, 18944, SEEK_SET) = 18944read(3, "\274e\214\27\33\21\201\374\216\365\3717|\201\254\n\267[;)\354\231\343\272\315\4\276\3007\275\204\353"..., 512) = 512lseek(3, 2048, SEEK_SET) = 2048read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1024) = 1024lseek(3, 2097152, SEEK_SET) = 2097152read(3, "0\210\1\5G\366\7\2u\n\211\356^\342\2111\\\342b\34\3011y\253]$z\3070\354\24\271"..., 1024) = 1024
close(3) = 0open("/etc/filesystems", O_RDONLY) = 3fstat(3, {st_mode=S_IFREG|0644, st_size=399, ...}) = 0mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f3f5a3a4000read(3, "# /etc/filesystems\n#\n# This file"..., 4096) = 399
close(3) = 0
munmap(0x7f3f5a3a4000, 4096) = 0
open("/proc/filesystems", O_RDONLY) = 3fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f3f5a3a4000 read(3, "nodev\tsysfs\nnodev\trootfs\nnodev\tb"..., 1024) = 213 stat("/sbin/mount.ext4", 0x7fff283f7550) = -1 ENOENT (No such file or directory) stat("/sbin/fs.d/mount.ext4", 0x7fff283f7550) = -1 ENOENT (No such file or directory) stat("/sbin/fs/mount.ext4", 0x7fff283f7550) = -1 ENOENT (No such file or directory) stat("/usr/sbin/mount.ext4", 0x7fff283f7550) = -1 ENOENT (No such file or directory) mount("/dev/sdc", "/mnt", "ext4", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) stat("/sbin/mount.vfat", 0x7fff283f7550) = -1 ENOENT (No such file or directory) stat("/sbin/fs.d/mount.vfat", 0x7fff283f7550) = -1 ENOENT (No such file or directory) stat("/sbin/fs/mount.vfat", 0x7fff283f7550) = -1 ENOENT (No such file or directory) stat("/usr/sbin/mount.vfat", 0x7fff283f7550) = -1 ENOENT (No such file or directory) mount("/dev/sdc", "/mnt", "vfat", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) stat("/sbin/mount.msdos", 0x7fff283f7550) = -1 ENOENT (No such file or directory) stat("/sbin/fs.d/mount.msdos", 0x7fff283f7550) = -1 ENOENT (No such file or directory) stat("/sbin/fs/mount.msdos", 0x7fff283f7550) = -1 ENOENT (No such file or directory) stat("/usr/sbin/mount.msdos", 0x7fff283f7550) = -1 ENOENT (No such file or directory) mount("/dev/sdc", "/mnt", "msdos", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) stat("/sbin/mount.iso9660", 0x7fff283f7550) = -1 ENOENT (No such file or directory) stat("/sbin/fs.d/mount.iso9660", 0x7fff283f7550) = -1 ENOENT (No such file or directory) stat("/sbin/fs/mount.iso9660", 0x7fff283f7550) = -1 ENOENT (No such file or directory) stat("/usr/sbin/mount.iso9660", 0x7fff283f7550) = -1 ENOENT (No such file or directory) mount("/dev/sdc", "/mnt", "iso9660", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) stat("/sbin/mount.xfs", 0x7fff283f7550) = -1 ENOENT (No such file or directory) stat("/sbin/fs.d/mount.xfs", 0x7fff283f7550) = -1 ENOENT (No such file or directory) stat("/sbin/fs/mount.xfs", 0x7fff283f7550) = -1 ENOENT (No such file or directory) stat("/usr/sbin/mount.xfs", 0x7fff283f7550) = -1 ENOENT (No such file or directory) mount("/dev/sdc", "/mnt", "xfs", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument)
read(3, "", 1024) = 0 close(3) = 0 munmap(0x7f3f5a3a4000, 4096) = 0
rt_sigprocmask(SIG_UNBLOCK, ~[TRAP SEGV RTMIN RT_1], NULL, 8) = 0 open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3fstat(3, {st_mode=S_IFREG|0644, st_size=2492, ...}) = 0mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f3f5a3a4000 read(3, "# Locale name alias data base.\n#"..., 4096) = 2492
read(3, "", 4096) = 0 close(3) = 0 munmap(0x7f3f5a3a4000, 4096) = 0
open("/usr/share/locale/en_US.UTF-8/LC_MESSAGES/util-linux.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US.utf8/LC_MESSAGES/util-linux.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en_US/LC_MESSAGES/util-linux.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en.UTF-8/LC_MESSAGES/util-linux.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en.utf8/LC_MESSAGES/util-linux.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/en/LC_MESSAGES/util-linux.mo", O_RDONLY) = -1 ENOENT (No such file or directory) write(2, "mount: you must specify the file"..., 43mount: you must specify the filesystem type) = 43 write(2, "\n", 1
) = 1exit_group(32) = ?
+++ exited with 32 +++
Signature · 6 lines
Markus _______________________________________________ xfs mailing list [email protected] http://oss.sgi.com/mailman/listinfo/xfs
Quoted 84 lines · Markus Trippelsdorf
Quoted 69 lines · Eric Sandeen
Quoted 68 lines · Markus Trippelsdorf
Quoted 66 lines · Eric Sandeen
Quoted 43 lines · Markus Trippelsdorf
Quoted 23 lines · Eric Sandeen
Quoted 16 lines · Markus Trippelsdorf
Today I accidentally tried to mount my backup disk at
/dev/sdcinstead of/dev/sdc1and this is what happened:...
EXT4-fs (sdc): VFS: Can't find ext4 filesystem
FAT-fs (sdc): bogus number of reserved sectors
FAT-fs (sdc): Can't find a valid FAT filesystem
FAT-fs (sdc): bogus number of reserved sectors
FAT-fs (sdc): Can't find a valid FAT filesystem
ISOFS: Unable to identify CD-ROM format.
XFS (sdc): bad magic numberffff8800db620000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ffff8800db620030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
XFS (sdc): Internal errorxfs_sb_read_verifyat line 726 of filefs/xfs/xfs_mount.c. Caller0xffffffff8119e5cdThis seems to be a recent regression.
Comments above
xfs_sb_quiet_read_verify()indicate that this behavior is to be avoided:Quoted 9 lines
* We may be probed for a filesystem match, so we may not want to emit
* messages when the superblock buffer is not actually an XFS superblock.and it checks for proper magic prior to all the chattiness above int that function.
The superblock read is suposed to choose whether to be noisy or not, in
xfs_readsb():The following patch fixes the issue for me:
fs/xfs/xfs_mount.c +0
-0@@ -721,6 +721,11 @@ xfs_sb_read_verify( }fs/xfs/xfs_mount.c xfs_sb_read_verify( · line 731
Quoted 10 lines
fs/xfs/xfs_mount.c +5
-0error =xfs_sb_verify (bp); +if (error ==XFS_ERROR (EWRONGFS )) { +xfs_buf_ioerror (bp,EWRONGFS ); +return ; + } + out_error:if (error) {XFS_CORRUPTION_ERROR (__func__,XFS_ERRLEVEL_LOW , mp, bp->b_addr);That might make sense, I don't think we need the loudness for EWRONGFS no matter how we got there.
But:
Out of curiosity, what was the actual mount command you used? It seems like the auto-probing should have set the
MS_SILENTflag to avoid this in the first place, i.e. we should have gone down the quiet path (xfs_sb_quiet_read_verify) and avoided this altogether.How do you reproduce this?
Quoted 8 lines
Quoted 3 lines
I power on the drive and simply run:
# mount /dev/sdc /mntInteresting. On my test box, that never even issues the mount syscall, because it uses blkid (I guess) to probe, and finds nothing.
Which util-linux do you have?
v2.21.2
Quoted 1 line
An strace -v of the mount command might be useful.
execve("/bin/mount", ["mount", "/dev/sdc", "/mnt"], [/* 44 vars */])= 0
...
Quoted 17 lines
stat("/sbin/mount.ext4", 0x7fff283f7550)= -1 ENOENT (No such file or directory)stat("/sbin/fs.d/mount.ext4", 0x7fff283f7550)= -1 ENOENT (No such file or directory)stat("/sbin/fs/mount.ext4", 0x7fff283f7550)= -1 ENOENT (No such file or directory)stat("/usr/sbin/mount.ext4", 0x7fff283f7550)= -1 ENOENT (No such file or directory)mount("/dev/sdc", "/mnt", "ext4", MS_MGC_VAL, NULL)= -1 EINVAL (Invalid argument)stat("/sbin/mount.vfat", 0x7fff283f7550)= -1 ENOENT (No such file or directory)stat("/sbin/fs.d/mount.vfat", 0x7fff283f7550)= -1 ENOENT (No such file or directory)stat("/sbin/fs/mount.vfat", 0x7fff283f7550)= -1 ENOENT (No such file or directory)stat("/usr/sbin/mount.vfat", 0x7fff283f7550)= -1 ENOENT (No such file or directory)mount("/dev/sdc", "/mnt", "vfat", MS_MGC_VAL, NULL)= -1 EINVAL (Invalid argument)stat("/sbin/mount.msdos", 0x7fff283f7550)= -1 ENOENT (No such file or directory)stat("/sbin/fs.d/mount.msdos", 0x7fff283f7550)= -1 ENOENT (No such file or directory)stat("/sbin/fs/mount.msdos", 0x7fff283f7550)= -1 ENOENT (No such file or directory)stat("/usr/sbin/mount.msdos", 0x7fff283f7550)= -1 ENOENT (No such file or directory)mount("/dev/sdc", "/mnt", "msdos", MS_MGC_VAL, NULL)= -1 EINVAL (Invalid argument)stat("/sbin/mount.iso9660", 0x7fff283f7550)= -1 ENOENT (No such file or directory)stat("/sbin/fs.d/mount.iso9660", 0x7fff283f7550)= -1 ENOENT (No such file or directory)
Quoted 8 lines
stat("/sbin/fs/mount.iso9660", 0x7fff283f7550)= -1 ENOENT (No such file or directory)stat("/usr/sbin/mount.iso9660", 0x7fff283f7550)= -1 ENOENT (No such file or directory)mount("/dev/sdc", "/mnt", "iso9660", MS_MGC_VAL, NULL)= -1 EINVAL (Invalid argument)stat("/sbin/mount.xfs", 0x7fff283f7550)= -1 ENOENT (No such file or directory)stat("/sbin/fs.d/mount.xfs", 0x7fff283f7550)= -1 ENOENT (No such file or directory)stat("/sbin/fs/mount.xfs", 0x7fff283f7550)= -1 ENOENT (No such file or directory)stat("/usr/sbin/mount.xfs", 0x7fff283f7550)= -1 ENOENT (No such file or directory)mount("/dev/sdc", "/mnt", "xfs", MS_MGC_VAL, NULL)= -1 EINVAL (Invalid argument)
Interesting, so it really does try to mount by successive fs types.
I wonder when that behavior changed (my util-linux-ng 2.17 on RHEL6 doesn't do this)
I'll take a look.
-Eric
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
On 5/6/13 3:49 PM, Eric Sandeen wrote:
...
Quoted 5 lines
Interesting, so [mount] really does try to mount by successive fs types.
I wonder when that behavior changed (my util-linux-ng 2.17 on RHEL6 doesn't do this)
I'll take a look.
Just to satisfy my curiosity:
commit c6c98f93f5e4b3fb9a8b51ed2ef9967793df7b1c
Author: Karel Zak <[email protected]> Date: Mon Mar 15 13:46:43 2010 +0100
mount: report ambivalent FS detection, improve brute force detection
The ambivalent probing result should be properly reported and user should be informed that the problem is possible to bypass by "-t <type>" or resolved by wipefs(8).
The mount(8) command uses a brute force stage (calls mount(2) for all /{proc,etc}/fylesystems) if there is not any other way how to detect the filesystem type. The brute force stage should not be restricted by libblkid. It's possible that libblkid is not able to detect slightly corrupted filesystem, but kernel is able to mount such filesystem.
Note that the brute force stage should not be used if libblkid returns ambivalent probing result. In this case user's intervention is required (e.g. mount -t <type>).
So we're getting into xfs mount with an actual "-t xfs" equivalent, and not going down the "silent" paths.
I'll send the patch.
Thanks,
-Eric
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
On 5/6/13 2:26 PM, Markus Trippelsdorf wrote:
...
Quoted 3 lines
OK, makes sense. Thanks.
I like your patch better, so lets use it.
Actually - why don't you go ahead & formally submit your patch with my suggested changes; it was your good idea to use EWRONGFS. :)
-Eric
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 31 lines · Eric Sandeen
On 5/6/13 3:49 PM, Eric Sandeen wrote:
...Quoted 5 lines
Interesting, so [mount] really does try to mount by successive fs types.
I wonder when that behavior changed (my util-linux-ng 2.17 on RHEL6 doesn't do this)
I'll take a look.
Just to satisfy my curiosity:
commit
c6c98f93f5e4b3fb9a8b51ed2ef9967793df7b1cAuthor: Karel Zak <[email protected]> Date: Mon Mar 15 13:46:43 2010 +0100mount: report ambivalent FS detection, improve brute force detection
The ambivalent probing result should be properly reported and user should be informed that the problem is possible to bypass by "-t <type>" or resolved by wipefs(8).
The mount(8) command uses a brute force stage (calls mount(2) for all /{proc,etc}/fylesystems) if there is not any other way how to detect the filesystem type. The brute force stage should not be restricted by libblkid. It's possible that libblkid is not able to detect slightly corrupted filesystem, but kernel is able to mount such filesystem.
Note that the brute force stage should not be used if libblkid returns ambivalent probing result. In this case user's intervention is required (e.g. mount -t <type>).
Quoted 5 lines
Reported-by Mike Frysinger <[email protected]>Signed-off-by Karel Zak <[email protected]>So we're getting into xfs mount with an actual "-t xfs" equivalent, and not going down the "silent" paths.
That's just completely broken mount behaviour. Probing is supposed to be *silent*, and this is just downright obnxious. Here's what I get in my log after doing this:
# dd if=/dev/zero of=/dev/vdb bs=512 count=1 # blkid -g # mount /dev/vdb /mnt/scratch/ mount: you must specify the filesystem type $ dmesg ...... [83182.775467] REISERFS warning (device vdb): sh-2021 reiserfs_fill_super: can not find reiserfs on vdb [83182.778473] EXT3-fs (vdb): error: can't find ext3 filesystem on dev vdb. [83182.781135] EXT2-fs (vdb): error: can't find an ext2 filesystem on dev vdb. [83182.783524] EXT4-fs (vdb): VFS: Can't find ext4 filesystem [83182.787392] cramfs: wrong magic [83182.788926] SQUASHFS error: Can't find a SQUASHFS superblock on vdb [83182.791150] VFS: Can't find a Minix filesystem V1 | V2 | V3 on device vdb. [83182.793737] FAT-fs (vdb): bogus number of reserved sectors [83182.795202] FAT-fs (vdb): Can't find a valid FAT filesystem [83182.797268] FAT-fs (vdb): bogus number of reserved sectors [83182.798984] FAT-fs (vdb): Can't find a valid FAT filesystem [83182.801236] BFS-fs: bfs_fill_super(): No BFS filesystem on vdb (magic=00000000) [83182.846555] ISOFS: Unable to identify CD-ROM format. [83182.849136] hfs: unable to find HFS+ superblock [83182.851164] hfs: can't find a HFS filesystem on dev vdb. [83182.853204] vxfs: WRONG superblock magic [83182.856855] VFS: unable to find oldfs superblock on device vdb [83182.858930] VFS: could not find a valid V7 on vdb. [83182.860938] NTFS-fs error (device vdb): read_ntfs_boot_sector(): Primary boot sector is invalid. [83182.863247] NTFS-fs error (device vdb): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover. [83182.866563] NTFS-fs error (device vdb): ntfs_fill_super(): Not an NTFS volume. [83182.873922] AFFS: No valid root block on device vdb [83182.875697] VFS: Can't find a romfs filesystem on dev vdb. [83182.877823] qnx4: wrong fsid in superblock. [83182.884286] UDF-fs: warning (device vdb): udf_load_vrs: No VRS found [83182.886217] UDF-fs: Rescanning with blocksize 2048 [83182.891965] UDF-fs: warning (device vdb): udf_load_vrs: No VRS found [83182.893730] UDF-fs: warning (device vdb): udf_fill_super: No partition found (1) [83182.896216] omfs: Invalid superblock (0) [83182.898937] XFS (vdb): bad magic number [83182.900150] ffff88007bbce000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [83182.902676] ffff88007bbce010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [83182.905281] ffff88007bbce020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [83182.907845] ffff88007bbce030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [83182.910559] XFS (vdb): Internal error xfs_sb_read_verify at line 726 of file fs/xfs/xfs_mount.c. Caller 0xffffffff814645e5 [83182.910559] [83182.914377] Pid: 1064, comm: kworker/0:1H Not tainted 3.9.0-rc8-dgc+ #575 [83182.916499] Call Trace: [83182.917245] [<ffffffff8146761f>] xfs_error_report+0x3f/0x50 [83182.918762] [<ffffffff814645e5>] ? xfs_buf_iodone_work+0xc5/0xf0 [83182.920113] [<ffffffff8146768e>] xfs_corruption_error+0x5e/0x90 [83182.921351] [<ffffffff814cf50a>] xfs_sb_read_verify+0x11a/0x130 [83182.922692] [<ffffffff814645e5>] ? xfs_buf_iodone_work+0xc5/0xf0 [83182.923972] [<ffffffff810b6555>] ? finish_task_switch+0x65/0x100 [83182.925343] [<ffffffff814645e5>] xfs_buf_iodone_work+0xc5/0xf0 [83182.926634] [<ffffffff810a35d0>] process_one_work+0x170/0x400 [83182.927832] [<ffffffff810a4f26>] worker_thread+0x116/0x390 [83182.929116] [<ffffffff810a4e10>] ? busy_worker_rebind_fn+0xb0/0xb0 [83182.930460] [<ffffffff810aadd8>] kthread+0xd8/0xe0 [83182.931469] [<ffffffff810aad00>] ? kthread_create_on_node+0x140/0x140 [83182.932921] [<ffffffff81c23dec>] ret_from_fork+0x7c/0xb0 [83182.934047] [<ffffffff810aad00>] ? kthread_create_on_node+0x140/0x140 [83182.935489] XFS (vdb): Corruption detected. Unmount and run xfs_repair [83182.937045] XFS (vdb): SB validate failed with error 22. [83182.940181] NILFS: Can't find nilfs on dev vdb. [83182.941321] BeFS(vdb): No write support. Marking filesystem read-only [83182.943036] BeFS(vdb): invalid magic header [83182.946526] (mount,23815,1):ocfs2_fill_super:1039 ERROR: superblock probe failed! [83182.948515] (mount,23815,1):ocfs2_fill_super:1230 ERROR: status = -22 [83182.951606] GFS2: not a GFS2 filesystem [83182.952898] GFS2: gfs2 mount does not exist [83182.954425] F2FS-fs (vdb): Magic Mismatch, valid(0xf2f52010) - read(0x49474158) [83182.956540] F2FS-fs (vdb): Can't find a valid F2FS filesystem in first superblock [83182.959044] F2FS-fs (vdb): Magic Mismatch, valid(0xf2f52010) - read(0x0) [83182.960894] F2FS-fs (vdb): Can't find a valid F2FS filesystem in second superblock
I've removed logfs from my kernels because this probing causes logfs to oops the kernel...
Quoted 1 line
I'll send the patch.
I think that mount needs fixing, not XFS. mount needs to be doing silent mounts when doing this brute forcing, not noisy, explicit mounts that we expect to throw errors if there is a problem.
Cheers,
Dave.
Signature · 7 lines
Dave Chinner [email protected] _______________________________________________ xfs mailing list [email protected] http://oss.sgi.com/mailman/listinfo/xfs
Quoted 42 lines · Dave Chinner
Quoted 31 lines · Eric Sandeen
On 5/6/13 3:49 PM, Eric Sandeen wrote:
...Quoted 5 lines
Interesting, so [mount] really does try to mount by successive fs types.
I wonder when that behavior changed (my util-linux-ng 2.17 on RHEL6 doesn't do this)
I'll take a look.
Just to satisfy my curiosity:
commit
c6c98f93f5e4b3fb9a8b51ed2ef9967793df7b1cAuthor: Karel Zak <[email protected]> Date: Mon Mar 15 13:46:43 2010 +0100mount: report ambivalent FS detection, improve brute force detection
The ambivalent probing result should be properly reported and user should be informed that the problem is possible to bypass by "-t <type>" or resolved by wipefs(8).
The mount(8) command uses a brute force stage (calls mount(2) for all /{proc,etc}/fylesystems) if there is not any other way how to detect the filesystem type. The brute force stage should not be restricted by libblkid. It's possible that libblkid is not able to detect slightly corrupted filesystem, but kernel is able to mount such filesystem.
Note that the brute force stage should not be used if libblkid returns ambivalent probing result. In this case user's intervention is required (e.g. mount -t <type>).
Quoted 5 lines
Reported-by Mike Frysinger <[email protected]>Signed-off-by Karel Zak <[email protected]>So we're getting into xfs mount with an actual "-t xfs" equivalent, and not going down the "silent" paths.
That's just completely broken mount behaviour. Probing is supposed to be *silent*, and this is just downright obnxious. Here's what I get in my log after doing this:
Quoted 10 lines
# dd if=/dev/zero of=/dev/vdb bs=512 count=1 # blkid -g # mount /dev/vdb /mnt/scratch/ mount: you must specify the filesystem type $ dmesg ...... [83182.775467] REISERFS warning (device vdb): sh-2021 reiserfs_fill_super: can not find reiserfs on vdb [83182.778473] EXT3-fs (vdb): error: can't find ext3 filesystem on dev vdb. [83182.781135] EXT2-fs (vdb): error: can't find an ext2 filesystem on dev vdb. [83182.783524] EXT4-fs (vdb): VFS: Can't find ext4 filesystem
....
BTW, strace indicates that MS_SILENT is not being used during brute force mounts:
# strace -vx mount /dev/vdb /mnt/scratch/ 2>&1 |grep ^mount
mount("/dev/vdb", "/mnt/scratch/", "reiserfs", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument)
mount("/dev/vdb", "/mnt/scratch/", "ext3", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument)
mount("/dev/vdb", "/mnt/scratch/", "ext2", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument)
mount("/dev/vdb", "/mnt/scratch/", "ext4", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument)
....So this really looks like a bug in mount, not the filesystem handling of slient mounts...
Cheers,
Dave.
Signature · 7 lines
Dave Chinner [email protected] _______________________________________________ xfs mailing list [email protected] http://oss.sgi.com/mailman/listinfo/xfs
Quoted 65 lines · Dave Chinner
Quoted 42 lines · Dave Chinner
Quoted 31 lines · Eric Sandeen
On 5/6/13 3:49 PM, Eric Sandeen wrote:
...Quoted 5 lines
Interesting, so [mount] really does try to mount by successive fs types.
I wonder when that behavior changed (my util-linux-ng 2.17 on RHEL6 doesn't do this)
I'll take a look.
Just to satisfy my curiosity:
commit
c6c98f93f5e4b3fb9a8b51ed2ef9967793df7b1cAuthor: Karel Zak <[email protected]> Date: Mon Mar 15 13:46:43 2010 +0100mount: report ambivalent FS detection, improve brute force detection
The ambivalent probing result should be properly reported and user should be informed that the problem is possible to bypass by "-t <type>" or resolved by wipefs(8).
The mount(8) command uses a brute force stage (calls mount(2) for all /{proc,etc}/fylesystems) if there is not any other way how to detect the filesystem type. The brute force stage should not be restricted by libblkid. It's possible that libblkid is not able to detect slightly corrupted filesystem, but kernel is able to mount such filesystem.
Note that the brute force stage should not be used if libblkid returns ambivalent probing result. In this case user's intervention is required (e.g. mount -t <type>).
Quoted 5 lines
Reported-by Mike Frysinger <[email protected]>Signed-off-by Karel Zak <[email protected]>So we're getting into xfs mount with an actual "-t xfs" equivalent, and not going down the "silent" paths.
That's just completely broken mount behaviour. Probing is supposed to be *silent*, and this is just downright obnxious. Here's what I get in my log after doing this:
Quoted 10 lines
# dd if=/dev/zero of=/dev/vdb bs=512 count=1 # blkid -g # mount /dev/vdb /mnt/scratch/ mount: you must specify the filesystem type $ dmesg ...... [83182.775467] REISERFS warning (device vdb): sh-2021 reiserfs_fill_super: can not find reiserfs on vdb [83182.778473] EXT3-fs (vdb): error: can't find ext3 filesystem on dev vdb. [83182.781135] EXT2-fs (vdb): error: can't find an ext2 filesystem on dev vdb. [83182.783524] EXT4-fs (vdb): VFS: Can't find ext4 filesystem....
BTW, strace indicates that
MS_SILENTis not being used during brute force mounts:# strace -vx mount /dev/vdb /mnt/scratch/ 2>&1 |grep ^mount mount("/dev/vdb", "/mnt/scratch/", "reiserfs", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) mount("/dev/vdb", "/mnt/scratch/", "ext3", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) mount("/dev/vdb", "/mnt/scratch/", "ext2", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) mount("/dev/vdb", "/mnt/scratch/", "ext4", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) ....
Quoted 2 lines
So this really looks like a bug in mount, not the filesystem handling of slient mounts...
Hm, good point, I forgot that mount could set MS_SILENT. . .
But still:
Do we really *ever* need this level of info when xfs discovers EWRONGFS?
-Eric
Quoted 4 lines
Cheers,
Dave.
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 66 lines · Eric Sandeen
Quoted 65 lines · Dave Chinner
Quoted 42 lines · Dave Chinner
Quoted 31 lines · Eric Sandeen
On 5/6/13 3:49 PM, Eric Sandeen wrote:
...Quoted 5 lines
Interesting, so [mount] really does try to mount by successive fs types.
I wonder when that behavior changed (my util-linux-ng 2.17 on RHEL6 doesn't do this)
I'll take a look.
Just to satisfy my curiosity:
commit
c6c98f93f5e4b3fb9a8b51ed2ef9967793df7b1cAuthor: Karel Zak <[email protected]> Date: Mon Mar 15 13:46:43 2010 +0100mount: report ambivalent FS detection, improve brute force detection
The ambivalent probing result should be properly reported and user should be informed that the problem is possible to bypass by "-t <type>" or resolved by wipefs(8).
The mount(8) command uses a brute force stage (calls mount(2) for all /{proc,etc}/fylesystems) if there is not any other way how to detect the filesystem type. The brute force stage should not be restricted by libblkid. It's possible that libblkid is not able to detect slightly corrupted filesystem, but kernel is able to mount such filesystem.
Note that the brute force stage should not be used if libblkid returns ambivalent probing result. In this case user's intervention is required (e.g. mount -t <type>).
Quoted 5 lines
Reported-by Mike Frysinger <[email protected]>Signed-off-by Karel Zak <[email protected]>So we're getting into xfs mount with an actual "-t xfs" equivalent, and not going down the "silent" paths.
That's just completely broken mount behaviour. Probing is supposed to be *silent*, and this is just downright obnxious. Here's what I get in my log after doing this:
Quoted 10 lines
# dd if=/dev/zero of=/dev/vdb bs=512 count=1 # blkid -g # mount /dev/vdb /mnt/scratch/ mount: you must specify the filesystem type $ dmesg ...... [83182.775467] REISERFS warning (device vdb): sh-2021 reiserfs_fill_super: can not find reiserfs on vdb [83182.778473] EXT3-fs (vdb): error: can't find ext3 filesystem on dev vdb. [83182.781135] EXT2-fs (vdb): error: can't find an ext2 filesystem on dev vdb. [83182.783524] EXT4-fs (vdb): VFS: Can't find ext4 filesystem....
BTW, strace indicates that
MS_SILENTis not being used during brute force mounts:# strace -vx mount /dev/vdb /mnt/scratch/ 2>&1 |grep ^mount mount("/dev/vdb", "/mnt/scratch/", "reiserfs", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) mount("/dev/vdb", "/mnt/scratch/", "ext3", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) mount("/dev/vdb", "/mnt/scratch/", "ext2", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) mount("/dev/vdb", "/mnt/scratch/", "ext4", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) ....
Quoted 8 lines
Quoted 2 lines
So this really looks like a bug in mount, not the filesystem handling of slient mounts...
Hm, good point, I forgot that mount could set
MS_SILENT. . .But still:
Do we really *ever* need this level of info when xfs discovers EWRONGFS?
Say, like when the autoprobe mount fails, and so you do a mount -t xfs to find out why it failed?
Perhaps the magic number is just fine (so blkid OKs it) and so the silent mount turns into a proper "noisy" mount and then we find a version number in the superblock that is not supported. That'll also throw a EWRONGFS error, and in that case the extra output will tell use exactly what went wrong.
Besides, the quiet verify path does not do an initial CRC check, and so if we do get a superblock CRC failure, it will dump something like this anyway....
Cheers,
Dave.
Signature · 7 lines
Dave Chinner [email protected] _______________________________________________ xfs mailing list [email protected] http://oss.sgi.com/mailman/listinfo/xfs
Re: Mount probing not silent. Internal error xfs_sb_read_verify at line 726
In reply to Dave ChinnerQuoted 114 lines · Dave Chinner
Quoted 11 lines · Eric Sandeen
On 5/6/13 3:49 PM, Eric Sandeen wrote:
...Quoted 5 lines
Interesting, so [mount] really does try to mount by successive fs types.
I wonder when that behavior changed (my util-linux-ng 2.17 on RHEL6 doesn't do this)
I'll take a look.
Just to satisfy my curiosity:
Quoted 8 lines
commit
c6c98f93f5e4b3fb9a8b51ed2ef9967793df7b1cAuthor: Karel Zak <[email protected]> Date: Mon Mar 15 13:46:43 2010 +0100mount: report ambivalent FS detection, improve brute force detection
So we're getting into xfs mount with an actual "-t xfs" equivalent, and not going down the "silent" paths.
That's just completely broken mount behaviour. Probing is supposed to be *silent*, and this is just downright obnxious. Here's what I get in my log after doing this:
# dd if=/dev/zero of=/dev/vdb bs=512 count=1 # blkid -g # mount /dev/vdb /mnt/scratch/ mount: you must specify the filesystem type $ dmesg ...... [83182.775467] REISERFS warning (device vdb): sh-2021 reiserfs_fill_super: can not find reiserfs on vdb [83182.778473] EXT3-fs (vdb): error: can't find ext3 filesystem on dev vdb. [83182.781135] EXT2-fs (vdb): error: can't find an ext2 filesystem on dev vdb. [83182.783524] EXT4-fs (vdb): VFS: Can't find ext4 filesystem [83182.787392] cramfs: wrong magic [83182.788926] SQUASHFS error: Can't find a SQUASHFS superblock on vdb [83182.791150] VFS: Can't find a Minix filesystem V1 | V2 | V3 on device vdb. [83182.793737] FAT-fs (vdb): bogus number of reserved sectors [83182.795202] FAT-fs (vdb): Can't find a valid FAT filesystem [83182.797268] FAT-fs (vdb): bogus number of reserved sectors [83182.798984] FAT-fs (vdb): Can't find a valid FAT filesystem [83182.801236] BFS-fs: bfs_fill_super(): No BFS filesystem on vdb (magic=00000000) [83182.846555] ISOFS: Unable to identify CD-ROM format. [83182.849136] hfs: unable to find HFS+ superblock [83182.851164] hfs: can't find a HFS filesystem on dev vdb. [83182.853204] vxfs: WRONG superblock magic [83182.856855] VFS: unable to find oldfs superblock on device vdb [83182.858930] VFS: could not find a valid V7 on vdb. [83182.860938] NTFS-fs error (device vdb): read_ntfs_boot_sector(): Primary boot sector is invalid. [83182.863247] NTFS-fs error (device vdb): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover. [83182.866563] NTFS-fs error (device vdb): ntfs_fill_super(): Not an NTFS volume. [83182.873922] AFFS: No valid root block on device vdb [83182.875697] VFS: Can't find a romfs filesystem on dev vdb. [83182.877823] qnx4: wrong fsid in superblock. [83182.884286] UDF-fs: warning (device vdb): udf_load_vrs: No VRS found [83182.886217] UDF-fs: Rescanning with blocksize 2048 [83182.891965] UDF-fs: warning (device vdb): udf_load_vrs: No VRS found [83182.893730] UDF-fs: warning (device vdb): udf_fill_super: No partition found (1) [83182.896216] omfs: Invalid superblock (0) [83182.898937] XFS (vdb): bad magic number [83182.900150] ffff88007bbce000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [83182.902676] ffff88007bbce010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [83182.905281] ffff88007bbce020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [83182.907845] ffff88007bbce030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [83182.910559] XFS (vdb): Internal error xfs_sb_read_verify at line 726 of file fs/xfs/xfs_mount.c. Caller 0xffffffff814645e5 [83182.910559] [83182.914377] Pid: 1064, comm: kworker/0:1H Not tainted 3.9.0-rc8-dgc+ #575 [83182.916499] Call Trace: [83182.917245] [<ffffffff8146761f>] xfs_error_report+0x3f/0x50 [83182.918762] [<ffffffff814645e5>] ? xfs_buf_iodone_work+0xc5/0xf0 [83182.920113] [<ffffffff8146768e>] xfs_corruption_error+0x5e/0x90 [83182.921351] [<ffffffff814cf50a>] xfs_sb_read_verify+0x11a/0x130 [83182.922692] [<ffffffff814645e5>] ? xfs_buf_iodone_work+0xc5/0xf0 [83182.923972] [<ffffffff810b6555>] ? finish_task_switch+0x65/0x100 [83182.925343] [<ffffffff814645e5>] xfs_buf_iodone_work+0xc5/0xf0 [83182.926634] [<ffffffff810a35d0>] process_one_work+0x170/0x400 [83182.927832] [<ffffffff810a4f26>] worker_thread+0x116/0x390 [83182.929116] [<ffffffff810a4e10>] ? busy_worker_rebind_fn+0xb0/0xb0 [83182.930460] [<ffffffff810aadd8>] kthread+0xd8/0xe0 [83182.931469] [<ffffffff810aad00>] ? kthread_create_on_node+0x140/0x140 [83182.932921] [<ffffffff81c23dec>] ret_from_fork+0x7c/0xb0 [83182.934047] [<ffffffff810aad00>] ? kthread_create_on_node+0x140/0x140 [83182.935489] XFS (vdb): Corruption detected. Unmount and run xfs_repair [83182.937045] XFS (vdb): SB validate failed with error 22. [83182.940181] NILFS: Can't find nilfs on dev vdb. [83182.941321] BeFS(vdb): No write support. Marking filesystem read-only [83182.943036] BeFS(vdb): invalid magic header [83182.946526] (mount,23815,1):ocfs2_fill_super:1039 ERROR: superblock probe failed! [83182.948515] (mount,23815,1):ocfs2_fill_super:1230 ERROR: status = -22 [83182.951606] GFS2: not a GFS2 filesystem [83182.952898] GFS2: gfs2 mount does not exist [83182.954425] F2FS-fs (vdb): Magic Mismatch, valid(0xf2f52010) - read(0x49474158) [83182.956540] F2FS-fs (vdb): Can't find a valid F2FS filesystem in first superblock [83182.959044] F2FS-fs (vdb): Magic Mismatch, valid(0xf2f52010) - read(0x0) [83182.960894] F2FS-fs (vdb): Can't find a valid F2FS filesystem in second superblockI've removed logfs from my kernels because this probing causes logfs to oops the kernel...
I think that mount needs fixing, not XFS. mount needs to be doing silent mounts when doing this brute forcing, not noisy, explicit mounts that we expect to throw errors if there is a problem.
BTW, strace indicates that
MS_SILENTis not being used during brute force mounts:# strace -vx mount /dev/vdb /mnt/scratch/ 2>&1 |grep ^mount mount("/dev/vdb", "/mnt/scratch/", "reiserfs", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) mount("/dev/vdb", "/mnt/scratch/", "ext3", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) mount("/dev/vdb", "/mnt/scratch/", "ext2", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) mount("/dev/vdb", "/mnt/scratch/", "ext4", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) ....
Quoted 2 lines
So this really looks like a bug in mount, not the filesystem handling of slient mounts...
So, lets CC util-linux...
Signature · 1 line
Markus
Re: Mount probing not silent. Internal error xfs_sb_read_verify at line 726
Quoted 94 lines · Markus Trippelsdorf
Quoted 93 lines · Dave Chinner
That's just completely broken mount behaviour. Probing is supposed to be *silent*, and this is just downright obnxious. Here's what I get in my log after doing this:
# dd if=/dev/zero of=/dev/vdb bs=512 count=1 # blkid -g # mount /dev/vdb /mnt/scratch/ mount: you must specify the filesystem type $ dmesg ...... [83182.775467] REISERFS warning (device vdb): sh-2021 reiserfs_fill_super: can not find reiserfs on vdb [83182.778473] EXT3-fs (vdb): error: can't find ext3 filesystem on dev vdb. [83182.781135] EXT2-fs (vdb): error: can't find an ext2 filesystem on dev vdb. [83182.783524] EXT4-fs (vdb): VFS: Can't find ext4 filesystem [83182.787392] cramfs: wrong magic [83182.788926] SQUASHFS error: Can't find a SQUASHFS superblock on vdb [83182.791150] VFS: Can't find a Minix filesystem V1 | V2 | V3 on device vdb. [83182.793737] FAT-fs (vdb): bogus number of reserved sectors [83182.795202] FAT-fs (vdb): Can't find a valid FAT filesystem [83182.797268] FAT-fs (vdb): bogus number of reserved sectors [83182.798984] FAT-fs (vdb): Can't find a valid FAT filesystem [83182.801236] BFS-fs: bfs_fill_super(): No BFS filesystem on vdb (magic=00000000) [83182.846555] ISOFS: Unable to identify CD-ROM format. [83182.849136] hfs: unable to find HFS+ superblock [83182.851164] hfs: can't find a HFS filesystem on dev vdb. [83182.853204] vxfs: WRONG superblock magic [83182.856855] VFS: unable to find oldfs superblock on device vdb [83182.858930] VFS: could not find a valid V7 on vdb. [83182.860938] NTFS-fs error (device vdb): read_ntfs_boot_sector(): Primary boot sector is invalid. [83182.863247] NTFS-fs error (device vdb): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover. [83182.866563] NTFS-fs error (device vdb): ntfs_fill_super(): Not an NTFS volume. [83182.873922] AFFS: No valid root block on device vdb [83182.875697] VFS: Can't find a romfs filesystem on dev vdb. [83182.877823] qnx4: wrong fsid in superblock. [83182.884286] UDF-fs: warning (device vdb): udf_load_vrs: No VRS found [83182.886217] UDF-fs: Rescanning with blocksize 2048 [83182.891965] UDF-fs: warning (device vdb): udf_load_vrs: No VRS found [83182.893730] UDF-fs: warning (device vdb): udf_fill_super: No partition found (1) [83182.896216] omfs: Invalid superblock (0) [83182.898937] XFS (vdb): bad magic number [83182.900150] ffff88007bbce000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [83182.902676] ffff88007bbce010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [83182.905281] ffff88007bbce020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [83182.907845] ffff88007bbce030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [83182.910559] XFS (vdb): Internal error xfs_sb_read_verify at line 726 of file fs/xfs/xfs_mount.c. Caller 0xffffffff814645e5 [83182.910559] [83182.914377] Pid: 1064, comm: kworker/0:1H Not tainted 3.9.0-rc8-dgc+ #575 [83182.916499] Call Trace: [83182.917245] [<ffffffff8146761f>] xfs_error_report+0x3f/0x50 [83182.918762] [<ffffffff814645e5>] ? xfs_buf_iodone_work+0xc5/0xf0 [83182.920113] [<ffffffff8146768e>] xfs_corruption_error+0x5e/0x90 [83182.921351] [<ffffffff814cf50a>] xfs_sb_read_verify+0x11a/0x130 [83182.922692] [<ffffffff814645e5>] ? xfs_buf_iodone_work+0xc5/0xf0 [83182.923972] [<ffffffff810b6555>] ? finish_task_switch+0x65/0x100 [83182.925343] [<ffffffff814645e5>] xfs_buf_iodone_work+0xc5/0xf0 [83182.926634] [<ffffffff810a35d0>] process_one_work+0x170/0x400 [83182.927832] [<ffffffff810a4f26>] worker_thread+0x116/0x390 [83182.929116] [<ffffffff810a4e10>] ? busy_worker_rebind_fn+0xb0/0xb0 [83182.930460] [<ffffffff810aadd8>] kthread+0xd8/0xe0 [83182.931469] [<ffffffff810aad00>] ? kthread_create_on_node+0x140/0x140 [83182.932921] [<ffffffff81c23dec>] ret_from_fork+0x7c/0xb0 [83182.934047] [<ffffffff810aad00>] ? kthread_create_on_node+0x140/0x140 [83182.935489] XFS (vdb): Corruption detected. Unmount and run xfs_repair [83182.937045] XFS (vdb): SB validate failed with error 22. [83182.940181] NILFS: Can't find nilfs on dev vdb. [83182.941321] BeFS(vdb): No write support. Marking filesystem read-only [83182.943036] BeFS(vdb): invalid magic header [83182.946526] (mount,23815,1):ocfs2_fill_super:1039 ERROR: superblock probe failed! [83182.948515] (mount,23815,1):ocfs2_fill_super:1230 ERROR: status = -22 [83182.951606] GFS2: not a GFS2 filesystem [83182.952898] GFS2: gfs2 mount does not exist [83182.954425] F2FS-fs (vdb): Magic Mismatch, valid(0xf2f52010) - read(0x49474158) [83182.956540] F2FS-fs (vdb): Can't find a valid F2FS filesystem in first superblock [83182.959044] F2FS-fs (vdb): Magic Mismatch, valid(0xf2f52010) - read(0x0) [83182.960894] F2FS-fs (vdb): Can't find a valid F2FS filesystem in second superblockI've removed logfs from my kernels because this probing causes logfs to oops the kernel...
I think that mount needs fixing, not XFS. mount needs to be doing silent mounts when doing this brute forcing, not noisy, explicit mounts that we expect to throw errors if there is a problem.
BTW, strace indicates that
MS_SILENTis not being used during brute force mounts:# strace -vx mount /dev/vdb /mnt/scratch/ 2>&1 |grep ^mount mount("/dev/vdb", "/mnt/scratch/", "reiserfs", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) mount("/dev/vdb", "/mnt/scratch/", "ext3", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) mount("/dev/vdb", "/mnt/scratch/", "ext2", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) mount("/dev/vdb", "/mnt/scratch/", "ext4", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) ....
Quoted 2 lines
Quoted 2 lines
So this really looks like a bug in mount, not the filesystem handling of slient mounts...
What about the following patch?
libmount/src/context_mount.c +1 -1
@@ -658,7 +658,7 @@ static int do_mount(struct libmnt_context *cxt, const char *try_type) type = try_type ? :mnt_fs_get_fstype (cxt->fs);if (!(flags &MS_MGC_MSK )) - flags |=MS_MGC_VAL ; + flags |= (MS_MGC_VAL |MS_SILENT ); DBG(CXT, mnt_debug_h(cxt, "%smount(2) " "[source=%s, target=%s, type=%s, "
Signature · 1 line
Markus
Karel Zak
maintainerRe: Mount probing not silent. Internal error xfs_sb_read_verify at line 726
In reply to Markus TrippelsdorfQuoted 5 lines · Markus Trippelsdorf
Quoted 4 lines · Dave Chinner
On Mon, May 06, 2013 at 04:48:39PM -0500, Eric Sandeen wrote:
I think that mount needs fixing, not XFS. mount needs to be doing silent mounts when doing this brute forcing, not noisy, explicit mounts that we expect to throw errors if there is a problem.
Good idea. Fixed.
Quoted 10 lines
Quoted 10 lines
BTW, strace indicates that
MS_SILENTis not being used during brute force mounts:# strace -vx mount /dev/vdb /mnt/scratch/ 2>&1 |grep ^mount mount("/dev/vdb", "/mnt/scratch/", "reiserfs", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) mount("/dev/vdb", "/mnt/scratch/", "ext3", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) mount("/dev/vdb", "/mnt/scratch/", "ext2", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) mount("/dev/vdb", "/mnt/scratch/", "ext4", MS_MGC_VAL, NULL) = -1 EINVAL (Invalid argument) ....
Quoted 4 lines
Quoted 2 lines
So this really looks like a bug in mount, not the filesystem handling of slient mounts...
So, lets CC util-linux...
Thanks.
Karel
Signature · 7 lines
Karel Zak <[email protected]> http://karelzak.blogspot.com _______________________________________________ xfs mailing list [email protected] http://oss.sgi.com/mailman/listinfo/xfs