search for: softupdates

Greetings, out of fun and to investigate claims about alleged bgfsck resource hogging (which I could not reproduce) posted to news:de.comp.os.unix.bsd, I pressed the reset button on a live FreeBSD 5-STABLE system. Upon reboot, fsck -p complained about an unexpected softupdates inconsistency on the / file system and put me into single user mode, the manual fsck / then asked me to agree to increasing a link count from 21 to 22 (and later to fix the summary, which I consider a non-issue). A subsequent fsck -p / ended with no abnormality detected. Unfortunately, I haven'...

Dear Samba team & other readers, I'm a satisfied user using Samba as a file server for Windows based networks and I'm primarily using FreeBSD for this purpose. When I started to use Samba about half a year ago, I was upset about the lousy performance but tried my best to search for that problem at myself. The machine at this time as a Pentium/200 PC with some SCSI harddisks and 64

...), weekly dumps of level 4 (each Sunday) and daily dumps of levels > 5 (each day except for Sunday - but including the firsts). dumps are done on live filesystems using -L. dumps are initially done to the same disk and only later are transfered to archive media. 2. both kernels are compiled with softupdates support but there are no filesystems with it enabled 3. both systems have root partition gmirror-ed, it is dumped 4. both systems have gjournal support (on 6.X it is added via a "non-official" patch), there are gjournaled filesystems on both systems and they are dumped. On June 1 (Sunday...

Hi there, System is FreeBSD 4.9 Stable Had a problem during a portupgrade that when portupgrade did some cleaning a directory could not be deleted because it were not empty. However, it was empty. rm -rf didn't help either. Because I didn't know what to do I decided to boot. At system startup fsck was started which produced the message: unexpected softupdate inconsistency and also that

Here's a patch against 4.8-RELEASE kernel that allows disk writes on softupdates-enabled filesystems to be delayed for (theoretically) arbitrarily long periods of time. The motivation for such updating policy is surprisingly not purely suicidal - it can allow disks on laptops to spin down immediately after I/O operations and stay idle for longer periods of time, thus saving con...

...S it has no useful effect at all, either unless soft > updates are turned on, which is not the default. > > Huh? That's not true at all. > > On ext3fs, the fsync() afterwards will flush the log, thus forcing the > link() to disk, just like it forces the link() to disk in softupdates. fsync() flushes the whole damned ext3 log? That would be lame. I expected they fixed that behavior long ago. Wietse - To unsubscribe, send mail to majordomo@postfix.org with content (not subject): unsubscribe postfix-users ----- End forwarded message ----- -- Ralf Hildebrandt (Im Auftrag de...

Sep 21 08:57:54 belle fsck: /dev/ad4s1d: 1 DUP I=190 Sep 21 08:57:54 belle fsck: /dev/ad4s1d: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. Ok, so I ran fsck manually (even with -y), but yet it refuses to clear/fix whatever to the questions posed as fsck runs. What does this all mean? Thanks, -Clint -- This message has been scanned for viruses and dangerous content by MailScanner,

So I have a system running: FreeBSD walk.dclg.ca 9.2-RC3 FreeBSD 9.2-RC3 # r254952: Wed Aug 28 03:02:55 EDT 2013 root at walk.dclg.ca:/usr/obj/usr/src/sys/STRIKE i386 and it has two 2T SATA disks. To keep this post short, the crash.txt is here. https://uk.eicat.ca/owncloud/public.php?service=files&t=fea9d25579fe0c4afb808859e80e1493 now curiously, while running a "make -j4

...y activity on the linux box). The main action I took with gentoo was to compile everything from scratch for my pc hardware, limiting the use of X & kde using all the above mentioned software prevailingly in a simple console. Now in a partition of the same laptop I installed freebsd 5.4, set softupdates, dma=1, and the same pieces of software as those I had installed under linux using the ports, therefore, compiling everything for my pc hardware, but, owing to my poor knowledge of Freebsd I'm experiencing some problems. In a nutshell I prepared the following test files: 1) a ConTeXt file...

Hello Rowland, thanks for your help. Below my comments Am Sa., 6. Apr. 2019 um 14:32 Uhr schrieb Rowland Penny via samba < samba at lists.samba.org>: > On Sat, 6 Apr 2019 10:58:15 +0200 > Martin Krämer via samba <samba at lists.samba.org> wrote: > > > Hello everyone, > > > > I have setup two Samba AD DC's running Debian 9 with BIND9_DLZ dns > >

...du procfs 4 4 0 100% /vm/1/mall.pgsql.com/proc <below>:/vm/.t/usr 239674416 205586740 24500700 89% /vm/1/mall.pgsql.com/usr Doing a 'df -t ufs' hangs as well, altho a straight 'df' runs through no problem ... /vm doesn't have softupdates enabled ... This is running a recent -STABLE: FreeBSD 4.8-STABLE #1: Fri Jun 6 01:22:46 ADT 2003

...did was mounting gjournaled partitions in ro mode (it warned me that they were not cleanly unmounted) and doing some backup. Then I removed gjournal (gjournal clear, tunefs -J disable) from journaled disks, ran fsck (few errors of type: PARTIALLY ALLOCATED INODE), and then I was able to turn on softupdates back and mount the fs in rw mode. I've double checked the disk's SMART results in case of hardware failure, but they were ok. My question is: what could cause such problem? Why only gjournaled fs are affected? Is there a solution? Best regards, -- _/_/ .. Eugene Butusov _/_/ ......

...ongest time to failure was 5 iterations. With out SMP the test ran with out problems for 570 iterations over 18 hours. We've tried a number of different tests. These tests are with a stock 6.1-RC1 kernel from the RC CD's. Unless otherwise specified, all tests are on a UFS2 filesystem with softupdates enabled and a SMP enabled GENERIC kernel. * !SMP: Ran 570 iterations in 18 hours with out a problem, test terminated by hand. * Large (190 GB) UFS2 filesystem with soft updates enabled and SMP kernel: Fails during the first iteration. * Medium (12 GB) UFS2 filesystem with soft...

Postfix <http://www.postfix.org> does a chattr +S on its spool directory when it is installed on Linux. This is what is written in the postfix startup script -- # # LINUX by default does not synchronously update directories - # that's dangerous for mail. # if [ -f /usr/bin/chattr ] then CHATTR="/usr/bin/chattr +S" else CHATTR=echo fi -- Is this still required on ext3 ?

...I've done this before many times, on this particular machine configure is failing with the error: no locking is available, running samba would be unsafe. I've googled and have seen this error, but no fixes. Any suggestions welcome. If it matters this is on a ufs2 filesystem with acls, and softupdates on it. It's also not mounted with any special mount options. Thanks. Dave.

postfix-users seems to be a subscription only list. I'd recommend incorporating TDMA <http://tdma.sf.net/> to allow for easy discussion by outsiders Andrew Morton (of ext3 fame) had sent this message to postfix-users list I am forwarding so that Wietse can hopefully provide the definitive answer to the question Andrew Morton/Stephen Tweedie seek ----- Forwarded message from Andrew

On Sat, 6 Apr 2019 17:21:26 +0200 Martin Krämer <mk.maddin at gmail.com> wrote: > Hello Rowland, > > thanks for your help. > Below my comments > > See here: > > > > http://apt.van-belle.nl/ > > > From stability point of view I always had the best experience by > saying with the debian default repository. > Additionally as you have seen blow I

...o be related to system load. It looks to me like a dangling pointer in softdep_update_inodeblock, but I am not very experienced in this area. The panics started recently when I was rewriting my firewall, so I suspected a bug in IPFW. The debug info below makes me think that the bug is related to softupdates. The panic is always a 'fatal trap 12'. The fault virtual address, fault code, code segment, processor eflags, and interupt mask is always the same. I am not sure about the pointers. Any suggestions? I can run more debug commands or whatever is helpful. Thanks in advance. Ben debugin...

I was using a GELI partition for /usr/home on 7.0, so it attaches and mounts on boot. The problem is it stopped working after the system was upgraded to RELENG_7/7.1-PRERELEASE. Here's how it goes: I have the following /etc/fstab: /dev/ad0s1b none swap sw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1d

...SD scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking #options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories #options MD_ROOT # MD is a potential root device options NFSCLIENT...