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 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

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,

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

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: $

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

Hi all! Several times now I have seen the following: fsck-ing the ext3 fs I get hundreds (if not thousands) of messages: Indoe NNNN, i_blocks is K, should be (K-8). FIXED: Interestingly the difference is *always* *always* *always* 8. Can someone explain me what was going on? Why this? Thanks a lot and all the best Norbert

Hiall! Is there un updated patch for bridge/nf/ebtables for 2.4.27? I tried the patch for 2.4.26 but there were several rejects. Then I patched in the rejects by hand and it zorked, at leqst for now. But to be sure I want someone with knowledge to update the patch instead of me nokey ;-) Best wishes Norbert -------------------------------------------------------------------------------

Processing commands for control at bugs.debian.org: > # bts housekeeping - fixing up versions to enable automatic bug archival > notfound 706747 3.2p1.4-28.1 Bug #706747 {Done: Andreas Beckmann <anbe at debian.org>} [olvwm] olvwm: fails to install [i386]: update-alternatives: error: alternative path /usr/bin/X11/olvwm-x-window-manager doesn't exist. There is no source info for the

Dear all, (please Cc) yesterday I had two bugs with btrfs and ext3 occurrences, always happening when plugging in an external USB btrfs disk. Today I had a BUG which is purely ext3 related. The last bug was with yesterdays latest git checkout. Here are the three bugs/oops: that one was with 3.0.0-rc2 (exactely) Jun 10 14:50:23 mithrandir kernel: [40871.704129] BUG: unable to handle kernel

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, >>

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

HI list! We regularly experience kernel Ooops on our alpha SX164 with ext3 on md on ide controller: No modules loaded, lsmod empty, self compiled kernel ksymoops 2.4.5 on alpha 2.4.25. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.25/ (default) -m /boot/System.map-2.4.25 (default) Warning: You did not tell me where

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