similar to: du hung, wild display in ps

Hi All, I've been tuning a server recently and just today this has started to appear in my top/htop output. [root at db1 ~]# ps -aux | grep kernel root 1011 0.0 0.0 212048 4532 ? Ss 13:34 0:00 /usr/bin/abrt-watch-log -F BUG: WARNING: at WARNING: CPU: INFO: possible recursive locking detected ernel BUG at list_del corruption list_add corruption do_IRQ: stack overflow: ear stack overflow

Hi, Please what is this error ? /usr/bin/abrt-watch-log -F BUG: WARNING: at WARNING: CPU: INFO: possible recursive locking detected ernel BUG at list_del corruption list_add corruption do_IRQ: stack overflow: ear stack overflow (cur: eneral protection fault nable to handle kernel ouble fault: RTNL: assertion failed eek! page_mapcount(page) went negative! adness at NETDEV WATCHDOG ysctl table

On 5/6/20 12:28 PM, Fred Smith wrote: > Was running du to examine the sizes of my backups and > found du hung, /mnt/backup is probably a network-mounted filesystem that is offline for one reason or another. You could try "umount -f /mnt/backup" if you can't get the mount working by any other means.? If that doesn't work, then "umount -l /mnt/backup" and

Hello again, I'm interested in manipulating some date objects, and have been playing with the difftime function. I'm not sure that this is the desired behavior: > pa$days.before.apr30 <- difftime(may01,as.POSIXct(pa$training.max,origin=as.POSIXct("1969-12-31 16:00:00",tz="PDT")),units="days") > units(pa$days.before.apr30) [1] "days" >

A new version of "the Matrix" (well, actually the R package named "Matrix") has become available on the CRAN mirrors. As some of you have noticed, the version numbers (current is version 0.999375-8) are converging to one, and we feel that we have solved enough of the many (mostly small) problems to announce that release 1.0-0 is imminent. In the DESCRIPTION of the package

A new version of "the Matrix" (well, actually the R package named "Matrix") has become available on the CRAN mirrors. As some of you have noticed, the version numbers (current is version 0.999375-8) are converging to one, and we feel that we have solved enough of the many (mostly small) problems to announce that release 1.0-0 is imminent. In the DESCRIPTION of the package

Hello R-help list, I have a piece of code written by a grad student here at BU which will segfault when using one data set, but complete just fine using another. Both sets are just text files full of real numbers. It seems like a bug within R. It could be a bug within her data, but again, her data is just a bunch of floats, so her data could be triggering a bug within R. I have tried this

moved to main samna list. On Tue, 01 May 2001 16:58:35 Patrick Goetz wrote: > > Here is a collection of problems I've encountered with > Samba 2.2 > > 1. Log files > > I configured Samba with --prefix=/opt/samba. Consequently, > by default, I get log files /opt/samba/var/log.nmbd > and /opt/samba/var/log.smbd . > > I'd prefer have a single log file

Hi All I am having an issue with disk space and since it is happening using an ext3 formatted partition I felt that this would be the most appropriate list to post to. The problem is this; I have access to two RHEL systems (one running RHEL3 and one running RHEL4). Both are in the same company and both exhibit the same problem that I have not seen anywhere else before. Both have full /

Just wondering if this is a bug... If I use the Linux 'du' command on a mounted samba share the reported disc usage is way off (though it seems to report bytes ok with the -b flag). Eg. it reports 1.3T of data instead of 2.7G. Maybe it's a du bug? 10:13 AM: du -sxh * 1.3T flac 458G mp3 10:13 AM: du -sxm * 1337366 flac 468124 mp3 10:13 AM: du -sxb * 2735172988 flac

(Sys config info at bottom) Use XP ntbackup.exe output to Samba share for several years and never had a problem. Backup size would range between 10 and 15 GB. Would always perform a verify after the backup. A few months ago the process started failing at the verify stage. The backup appeared to complete successfully, but as soon as the verify process started a message "Error: An

Hi, I updated my R rpms for SuSE systems. They are now available both for S.u.S.E 5.3 and SuSE 6.0 under ftp://ftp.ci.tuwien.ac.at/pub/R/bin/linux/suse/ Additionally I put binaries for DEC Alpha systems running Digital Unix 4.0 under ftp://ftp.ci.tuwien.ac.at/pub/R/bin/osf/osf4.0/alpha/ These packages are available as rpms and as a setld kit. setld is the Digital Unix package maintanance

Je lirai votre message avec int?r?t ? mon retour lundi 23 mai Cordialement Anne-Fran?oise Mar?s Anne-Fran?oise Mar?s Cordialement Anne-Fran?oise Mar?s

This patch set nukes all the dummy crtc mode_fixup implementations. (made on top of Daniel topic/drm-misc branch) Signed-off-by: Carlos Palminha <palminha at synopsys.com> --- drivers/gpu/drm/rcar-du/rcar_du_crtc.c | 9 --------- 1 file changed, 9 deletions(-) diff --git a/drivers/gpu/drm/rcar-du/rcar_du_crtc.c b/drivers/gpu/drm/rcar-du/rcar_du_crtc.c index 4ec80ae..627abc80 100644 ---

The rcar-du driver uses an empty implementation for its encoder. Replace the code with the generic simple encoder. Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de> --- drivers/gpu/drm/rcar-du/rcar_du_encoder.c | 14 +++----------- 1 file changed, 3 insertions(+), 11 deletions(-) diff --git a/drivers/gpu/drm/rcar-du/rcar_du_encoder.c b/drivers/gpu/drm/rcar-du/rcar_du_encoder.c

вт, 18 лют. 2020 о 10:48 Richard W.M. Jones <rjones@redhat.com> пише: > > When calculating the initial size of the disk we must estimate > how much space is taken by the input. This is quite difficult. > > For directories we used ‘du --apparent-size -bs DIR’. This is wrong > because ’-b’ implies ‘--apparent-size --block-size=1’. But also > ‘--apparent-size’ causes du

> I think it's a difficult problem and one which won't be solved using > du. For comparison we have some nbdkit plugins for creating > filesystems and they are far more sophisticated, especially this one: > https://github.com/libguestfs/nbdkit/tree/master/plugins/floppy > > I would note that the reason the test fails was nothing to do with > free space. It was

Hi all, I'm having fun getting to know xfs_quotas. I do notice some irregularities. When running xfs_quota -s -c /dev/sdc1 And then running report -h, for user barney, his used space is 4.9G while his soft/hard limit is 5G. Since I set 5, all is well, but when I run du -hs on barnies dir, it shows only 4G used. I can adjust for the diff so that my quotas can be set to 6G when I

https://www1.montpellier.inra.fr/intranet/intracampus/logiciels/consult/

Recently after installing Amanda backup I discovered that the smbclient du command doesn't really work correctly. If recurse in on, du starts at '/', with recurse off and no arg, 0 is returned. If the mask '*' is passed, only files without a dot in the filename are considered. With '*.*' all files are considered and du sums only the files in the current directory, no