similar to: rsync 3.0.9 incompatible with self? (proto incompat on local->local)

---- I have a bunch of these in my log... Was wondering if anyone had seen them before and what the cause might be? Thanks... Oct 1 03:25:15 Ishtar smbd[23925]: [2011/10/01 03:25:15, 0] lib/util.c:1468(smb_panic) Oct 1 03:25:15 Ishtar smbd[23925]: PANIC (pid 23925): internal error Oct 1 03:25:15 Ishtar smbd[23925]: #1 /usr/sbin/smbd(smb_panic+0x55) [0x7f7120093134] Oct 1 03:25:15

https://bugzilla.samba.org/show_bug.cgi?id=5407 Summary: hlink.c:480: finish_hard_link: Assertion `flist != ((void *)0)' failed. Product: rsync Version: 3.0.2 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo:

Hi, I'm having a problem using --link-dest and --hard-links when the fs hits the hard link limit (link(2) returns EMLINK). Using rsync 3.0.7 an error is thrown and the target file is not created. Glancing at git head it _looks_ like things could now be a little nicer. Perhaps the target file is copied instead of hard linked when hardlinking fails -- I've not tested it. Anyway, the

The only thing related to 'addresses' in my /etc/samba/smb.conf file is a "hosts allow": hosts allow = 192.168.3.0/24 127.1 I'm going to ignore the 'local hosts case, as if I solve the other, the localhost case may get solved by inference. I thought the 'hosts allow' would allow any host on the local 192.168.3.0/24 subnet. The hosts have no problems

https://bugzilla.samba.org/show_bug.cgi?id=7454 Summary: assertion failed in finish_hard_link() Product: rsync Version: 3.0.7 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: bas at debian.org

After an upgrade, I got re-bitten by the 'unix-extensions and wide links' incompat. (They used to be compat but were made incompat in the 3.4.x timeframe due to security concerns). At the time it was suggested I write a patch complete with documentation to describe the fix. The below seems to fit the bill. I was wondering what people thought about it's inclusion in future

Older kernels would generally be able to still mount the filesystem with the default subvolume set, but it would result in a different volume being mounted, which could be an even more unpleasant suprise for users. So if you set your default subvolume, you can''t go back to older kernels. Thanks, Signed-off-by: Josef Bacik <josef@redhat.com> --- fs/btrfs/ctree.h | 4 +++-

In support of the recently added capability to remount with lzo compression, provide a helper function to check the compression INCOMPAT flags when remounting with lzo compression, and set the flags if necessary. Also, implement the new helper function when defragmenting with explicit lzo compression and when setting the default subvolume. Signed-off-by: Mitch Harder

This adds the flag to ctree.h, adds the feature option to mkfs to turn it on and fixes fsck so it doesn''t complain about missing hole extents in files when this flag is set. Signed-off-by: Josef Bacik <jbacik@fusionio.com> --- cmds-check.c | 14 ++++++++++++-- ctree.h | 5 +++-- mkfs.c | 2 ++ 3 files changed, 17 insertions(+), 4 deletions(-) diff --git

Signed-off-by: Anand Jain <anand.jain@oracle.com> --- mkfs.c | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) diff --git a/mkfs.c b/mkfs.c index de1beed..0843600 100644 --- a/mkfs.c +++ b/mkfs.c @@ -1196,8 +1196,7 @@ static void process_fs_features(u64 flags) for (i = 0; i < ARRAY_SIZE(mkfs_features); i++) { if (flags & mkfs_features[i].flag) { - fprintf(stderr,

The following case will make the incompat/compat flag of the super block be recovered. Task1 |Task2 flags = btrfs_super_incompat_flags(); | |flags = btrfs_super_incompat_flags(); flags |= new_flag1; | |flags |= new_flag2; btrfs_set_super_incompat_flags(flags); | |btrfs_set_super_incompat_flags(flags); the new_flag1 is recovered. In order to avoid this problem, we

Hi! When i'm running debugfs.ocfs2 i get the following result: debugfs.ocfs2 -R "stats" /dev/sdb Revision: 0.90 Mount Count: 0 Max Mount Count: 20 State: 0 Errors: 0 Check Interval: 0 Last Check: Mon May 10 12:17:37 2010 Creator OS: 0 Feature Compat: 3 backup-super strict-journal-super Feature Incompat: 8016 sparse

I have a dir "dir/" with 2 dirs in it "a/" and "b/". dir b/ has a file in it 'file' dir a has a relative symlink to that file: Ishtar:/tmp> ll dir total 0 drwxrwxr-x 2 20 Mar 26 10:51 a/ drwxrwxr-x 2 17 Mar 26 10:49 b/ Ishtar:/tmp> ll dir/{a,b} dir/a: total 0 lrwxrwxrwx 1 9 Mar 26 10:51 symfile -> ../b/file dir/b: total 0 -rw-rw-r-- 1 0 Mar 26

OK. Digging into this... sendmail.m4 has the lines: define(`FAX_MAILER_PATH',`/usr/bin/faxmail')dnl define(`FAX_MAILER_ARGS',`faxmail -d -n -p 12pt $u@$h $f')dnl MAILER(`fax')dnl proto.m4 has: `R$+ < @ $+ .FAX. > $#fax $@ $2 $: $1 user at host.FAX', `ifdef(`FAX_RELAY', `R$*<@$+.FAX.>$* $:

Any help about this error on domU ? request_module: runaway loop modprobe net-pf-16-proto-9 request_module: runaway loop modprobe net-pf-16-proto-9 request_module: runaway loop modprobe net-pf-16-proto-9 request_module: runaway loop modprobe net-pf-16-proto-9 request_module: runaway loop modprobe net-pf-16-proto-9 I am using xen_changeset : Sat Apr 1 14:59:12 2006 +0100

Any help about this error on domU ? request_module: runaway loop modprobe net-pf-16-proto-9 request_module: runaway loop modprobe net-pf-16-proto-9 request_module: runaway loop modprobe net-pf-16-proto-9 request_module: runaway loop modprobe net-pf-16-proto-9 request_module: runaway loop modprobe net-pf-16-proto-9 I am using xen_changeset : Sat Apr 1 14:59:12 2006 +0100

Hi all: Sorry for my ignorance but I don't understand these log entries: Feb 25 04:18:24 munin Shorewall:net2fw:DROP: IN=eth0 OUT= MAC=48:5b:39:ac:1b:5e: 00:12:da:a4:14:bf:08:00 SRC=95.211.197.1 DST=81.166.42.2 LEN=60 TOS=00 PREC=0x00 TTL=120 ID=1036 PROTO=255 MARK=0 Feb 25 04:18:25 munin Shorewall:net2fw:DROP: IN=eth0 OUT= MAC=48:5b:39:ac:1b:5e: 00:12:da:a4:14:bf:08:00 SRC=95.211.197.1

xcb-proto 1.2 is now available. Rejoice! Bart Massey (1): fixed xv SelectPortNotify argument; bug reported by Julien Cristau <jcristau at debian.org> Eamon Walsh (14): Add XML description for XInput extension. Add XML description for SELinux extension. xcb-xselinux: Remove an errant padding statement. xcb-xselinux: Revisions to xselinux extension protocol.

Hello, It seems that the following restriction is not shown in the online man page for tcrules: ERROR: SOURCE/DEST PORT(S) not allowed with PROTO all : /tmp/shorewall/tcrules (line 2) Please let me know if this is expressed otherwise in the documentation. Thanks. ------------------------------------------------------------------------------ EditLive Enterprise is the world''s most

https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=543 Summary: ANY shows as 0 for proto on 1.3.7 Product: iptables Version: unspecified Platform: All OS/Version: other Status: NEW Severity: minor Priority: P2 Component: iptables AssignedTo: laforge@netfilter.org ReportedBy: