similar to: problems with usb stick after suspend and wake up

Hi Alan, thanks for your answer. > I do not recognize this problem based on your description. Please post > the dmesg log. Here cleaned output of journalctl, removed mainly networkmanager stuff. This is about a wake up after sleep, where before the stick was ok. More details necessary, let me know. Thanks Norbert

Hi Alan, sorry for the journalctl output. I have now done the following:L * boot into 3.17-rc7 * mount the usb stick (recovery completed) * unmount, mount, unmount - just to be sure all is fine * started usbmon capturing on bus 3 * mount the usb stick * suspend to ram * wake up now the stick is "officially" mounted (/proc/mounts) * umount error messages pop up * try to mount more

On Sat, 27 Sep 2014, Norbert Preining wrote: > Dear all, > > (please Cc) > > I am running latest kernel (3.17-rc6) and I see corruption of an usb3.0 > device usb stick. Strange errors, impossibility to mount. > > Repeated unplugging and replugging helps sometimes, in all cases > recovery is necessary. > > Is this a know problem, a problem of my system >

On Sun, 28 Sep 2014, Norbert Preining wrote: > Hi Alan, > > thanks for your answer. > > > I do not recognize this problem based on your description. Please post > > the dmesg log. > > Here cleaned output of journalctl, removed mainly networkmanager stuff. I would have preferred to see the output from dmesg, as I requested. But never mind, there probably

On Mon, 29 Sep 2014, Norbert Preining wrote: > Hi Alan, > > sorry for the journalctl output. I have now done the following:L > > * boot into 3.17-rc7 > * mount the usb stick (recovery completed) > * unmount, mount, unmount - just to be sure all is fine > * started usbmon capturing on bus 3 > * mount the usb stick > * suspend to ram > * wake up > now the

Hi! I was testing 2.6.0-test5, but got lots of journal aborted errors. Then I Sysrq-s/u/b and wanted to boot 2.4.23-pre3 or 2.4.22, but ext3 error: cannot find root fs cannot mount because of unsupported optional feature (4) after trying to mount it with ext2 (rootfstype=ext2, not working) I rebooted again into 2.4.22, this time there was just severe fs corrpution, illegal blocks, inodes,

Hi all! I have a slight problem: I have an external disk which contains one big filesystem (like a floppy) type ext3 (If you ask why: blame udev or maxtor, or me because I am stupid) which is approx 60% filled. Now I want to have a partition table, ie a layout where the current filesystem is the first partition, and the rest is as usual. Is this possible withotu destroying the data? Best

An update to the ext3 filesystem for 2.4 kernels is available at http://www.uow.edu.au/~andrewm/linux/ext3/ The diffs are against linux-2.4.7 and linux-2.4.6-ac5. The changelog is there. One rarely-occurring but oopsable bug was fixed and several quite significant performance enhancements have been made. These are in addition to the performance fixes which went into 0.9.3. Ted has put out a

There's a new set of ext2/3 patches for 2.4.21-pre5 available at: http://thunk.org/tytso/linux/extfs-2.4-update/extfs-update-2.4.21pre5-2 and in broken out form at: http://thunk.org/tytso/linux/extfs-2.4-update/broken-out-2.4.21pre5-2 New to this patch set include: * A kludge to help htree work well with Linux's NFS implementation * Allow the orlov allocator to be disabled via a

Hello, Seeing a strange thing with dovecot 1.0 b7 pop3. If a user gets a particular _very_ short spam message (not sure what virus makes these..), with NO Subject and NO To: headers and NO body, (example available upon request), the user is unable to download the mail. The log entry is: May 10 10:51:35 mail dovecot: POP3(user): Disconnected top=0/0, retr=1/1344, del=0/75, size=16383381

Thanks for reading this email?I found a problem while using Glusterfs? First?I created a Distributed Dispersed volume on three nodes?and Limit the volume capacity use quota command?this volume is auto mounted on /run/gluster/VOLUME_NAME. This volume can be read and written normally? After, I manually mounted the volume in another path to provide data storage of SAMBA and ISCSI services, after

Would it be a usefull addition to memdisk's "pause" parameter if it showed the loading speed for the specified disk image file? The idea is to verify if a device is really loading an operating system's data at the intended device/controller/interface/bus (etc) speed. My own system has a habit of setting usb2.0 interface to 1.1-speeds for example. With (hopefully) bootable

On 27 January 2016 at 18:09, mathias dufresne <infractory at gmail.com> wrote: > Use the same krb5.conf on members as on DC, no? > > Tried... same error msg. > 2016-01-27 7:42 GMT+01:00 Henry McLaughlin <henry at incred.com.au>: > >> On 27 January 2016 at 17:40, mathias dufresne <infractory at gmail.com> >> wrote: >> >> > Hi, >>

Hi rsync gurus! [Please Cc: me, as I am NOT subscribed to the list!] First the data points: debian/woody, local server=i386 arch, remote is alpha arch rsync version on both debian 2.5.5-0.2 While upgrading our server to a raid we were hit by a bug which I really consider very strange: The option -n/--dry-run does NOT change files, but DELETE files when called with --delete. Test case I had: $

Is there any documentation available about what block size MEMDISK uses to load (big iso/harddisk) image files? Experimenting with cptime.c32 on a Lexar Triton Jumpdrive (64GB, 170MB/s read in Windows, 150MB/s write in Windows) on bootable USB3.0 resulted in the following, depending on specified block size: * 2048 bytes --> 25MB/s * 2MB --> 61MB/s It would be nice to know at which speed

I was reading the Wiki page here: http://wiki.xen.org/wiki/VTd_HowTo don''t know how updated it is, BUT at the top it said: -------------------- -------------------- -------------------- -------------------- -------------------- -------------------- _Xen 4.1 xl tools notes _ * Only devices with FLR capabilities are supported. * Passing through a PCI card without FLR capability

Hi all, I'm booting Centos6 from a usb 3.0 stick. This works fine as long as the usb-stick is connected to a usb 2.0 port. Once I plug the the usb-stick into a blue usb 3.0 port centos fails on mounting the root filesystem. Any hints on that? Regards .....Volker

On Sun, Nov 17, 2013 at 2:12 AM, Michael B Allen <ioplex at gmail.com> wrote: > The problem is USB. I have an external keyboard+mouse connected by USB > and if I remove it I can successfully suspend and resume. If I plug in > a USB MIDI keyboard, again, I cannot suspend. So it seems any USB > connection breaks suspend. It seems I have fixed the problem! If I disable the

On Nov 25, 2014, at 8:17 PM, Victor Porton <porton at narod.ru> wrote: > Well, also below in dmesg: > > [ 190.249219] usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 -110 is -ETIMEDOUT. > 26.11.2014, 03:05, "Victor Porton" <porton at narod.ru>: >> A fragment of dmesg output (here idVendor=0665, idProduct=5161 is the

hi All, There is a distributed cluster with 5 bricks: gl0 Filesystem Size Used Avail Use% Mounted on /dev/sda4 5.5T 4.1T 1.5T 75% /mnt/brick1 gl1 Filesystem Size Used Avail Use% Mounted on /dev/sda4 5.5T 4.3T 1.3T 78% /mnt/brick1 gl2 Filesystem Size Used Avail Use% Mounted on /dev/sda4 5.5T 4.1T 1.4T 76% /mnt/brick1 gl3 Filesystem Size Used