linux-ext4 - Re: Weird I/O errors with USB hard drive not remounting filesystem readonly

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.0911231533071.2958-100000@iolanthe.rowland.org>
Date:	Mon, 23 Nov 2009 15:33:56 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	tmhikaru@...il.com
cc:	Jan Kara <jack@...e.cz>, <linux-kernel@...r.kernel.org>,
	<linux-usb@...r.kernel.org>, Jens Axboe <axboe@...nel.dk>,
	<linux-scsi@...r.kernel.org>, <linux-ext4@...r.kernel.org>
Subject: Re: Weird I/O errors with USB hard drive not remounting filesystem
 readonly

On Mon, 23 Nov 2009 tmhikaru@...il.com wrote:

> Uhh, this could be a problem. CONFIG_USB_MON=y is set in my .config BUT,
> although I followed the directions and debugfs is mounted,
> 
> root@...l:/home/tm# mount
> /dev/root on / type ext4 (rw,relatime,barrier=1,data=ordered,data_err=abort)
> proc on /proc type proc (rw)
> sysfs on /sys type sysfs (rw)
> usbfs on /proc/bus/usb type usbfs (rw)
> none_debugs on /sys/kernel/debug type debugfs (rw)
> 
> I receive this message when I test if usbmon's directory exists:
> 
> root@...l:/home/tm# ls /sys/kernel/debug/usbmon
> ls: cannot access /sys/kernel/debug/usbmon: No such file or directory
> 
> According to the kernel documentation usbmon should be loaded already. Help?

The documentation is slightly out of date.  The usbmon directory has 
been moved down a level, to /sys/kernel/debug/usb/usbmon.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html