Re: FreeBSD 10.2-RELEASE #0 r286666: Panic and crash

[Shawn Bakhtiar]

Well

It happened again today.

I found a few instances on the web of others reporting similar issues, and also 
ran across this bug.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211037

This is early similar to what is happening to me, save that in this case it's 
happening with a USB drive. Should I be attaching this there?

I've disabled the local backup to the USB (just doing the remote one to the 
share drive).

Any help would be greatly appreciated.


On Feb 6, 2017, at 1:01 PM, Shaheen Bakhtiar 
> wrote:

Hi all!

http://pastebin.com/niXrjF0D

Please refer to full output from crash above.

This morning our IMAP server decided to go belly up. I could not remote in, and 
the machine would not respond to any pings.

Checking the physical console I had the following worrisome messages on screen:

• g_vfs_done():da1p1[READ(offset=7265561772032, length=32768)]error = 5
• g_vfs_done():da1p1[WRITE(offset=7267957735424, length=131072)]error = 16
• /mnt/USBBD: got error 16 while accessing filesystem
• panic: softdep_deallocate_dependencies: unrecovered I/O error
• cpuid = 5

/mnt/USBDB is a MyBook USB 8TB drive that we use for daily backups of the IMAP 
data using rsync. Everything so far has worked without issue.

I also noticed a bunch of:

• fstat: can't read file 2 at 0x41f
• fstat: can't read file 4 at 0x78
• fstat: can't read file 5 at 0x6
• fstat: can't read file 1 at 0x27f
• fstat: can't read file 2 at 0x41f
• fstat: can't read file 4 at 0x78
• fstat: can't read file 5 at 0x6


but I have no idea what these are from.

df -h output:
/dev/da0p21.8T226G1.5T13%/
devfs 1.0K1.0K  0B   100%/dev
/dev/da1p17.0T251G6.2T 4%/mnt/USBBD


da0p2 is a RAID level 5 on an HP Smart Array

Here is the output of dmsg after reboot:
http://pastebin.com/rHVjgZ82

Obviously both the RAID and USB drive did not walk away from the crash 
cleaning. Should I be running a fsck at this point on both from single user 
mode to verify and clean up. My concern is the:
WARNING: /: mount pending error: blocks 0 files 26
when mounting /dev/da0p2

For some reason I was under the impression that fsck was run automatically on 
reboot.

Any help in this matter would be greatly appreciated. I'm a little concerned 
that a backup strategy that has worked for us for many MANY years would so 
easily throw the OS into panic. If an I/O error occurred on the USB Drive I 
would frankly think it should just back out, without panic. Or am I missing 
something?

Any recommendations / insights would be most welcome.
Shawn









___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

FreeBSD 10.2-RELEASE #0 r286666: Panic and crash

[Shawn Bakhtiar]

Hi all!

http://pastebin.com/niXrjF0D

Please refer to full output from crash above.

This morning our IMAP server decided to go belly up. I could not remote in, and 
the machine would not respond to any pings.

Checking the physical console I had the following worrisome messages on screen:

• g_vfs_done():da1p1[READ(offset=7265561772032, length=32768)]error = 5
• g_vfs_done():da1p1[WRITE(offset=7267957735424, length=131072)]error = 16
• /mnt/USBBD: got error 16 while accessing filesystem
• panic: softdep_deallocate_dependencies: unrecovered I/O error
• cpuid = 5

/mnt/USBDB is a MyBook USB 8TB drive that we use for daily backups of the IMAP 
data using rsync. Everything so far has worked without issue.

I also noticed a bunch of:

• fstat: can't read file 2 at 0x41f
• fstat: can't read file 4 at 0x78
• fstat: can't read file 5 at 0x6
• fstat: can't read file 1 at 0x27f
• fstat: can't read file 2 at 0x41f
• fstat: can't read file 4 at 0x78
• fstat: can't read file 5 at 0x6


but I have no idea what these are from.

df -h output:
/dev/da0p21.8T226G1.5T13%/
devfs 1.0K1.0K  0B   100%/dev
/dev/da1p17.0T251G6.2T 4%/mnt/USBBD


da0p2 is a RAID level 5 on an HP Smart Array

Here is the output of dmsg after reboot:
http://pastebin.com/rHVjgZ82

Obviously both the RAID and USB drive did not walk away from the crash 
cleaning. Should I be running a fsck at this point on both from single user 
mode to verify and clean up. My concern is the:
WARNING: /: mount pending error: blocks 0 files 26
when mounting /dev/da0p2

For some reason I was under the impression that fsck was run automatically on 
reboot.

Any help in this matter would be greatly appreciated. I'm a little concerned 
that a backup strategy that has worked for us for many MANY years would so 
easily throw the OS into panic. If an I/O error occurred on the USB Drive I 
would frankly think it should just back out, without panic. Or am I missing 
something?

Any recommendations / insights would be most welcome.
Shawn








___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Error with auto mount

[Shawn Bakhtiar]

Never mind...

Answered my own question

Needed to follow the instructions here to delete existing partition off the 
drive and re-creat a new partition

https://www.freebsd.org/doc/en/books/handbook/disks-adding.html

It looks like FreeBSD either does not support or does not understand the 
default partition on the Western Digital

It was:

root@correo:/ # gpart show /dev/da1
=> 34  15628052413  da1  GPT  (7.3T)
   34 2014   - free -  (1.0M)
 2048  156280483841  ms-basic-data  (7.3T)
  15628050432 2015   - free -  (1.0M)

Changed it to:
root@correo:/mnt/USBBD # gpart show /dev/da1
=> 34  15628052413  da1  GPT  (7.3T)
   34 2014   - free -  (1.0M)
 2048  156280483841  freebsd-ufs  (7.3T)
  15628050432 2015   - free -  (1.0M)


added it to my fstab:
# DeviceMountpoint  FStype  Options DumpPass#
/dev/da0p2  /   ufs rw  1   1
/dev/da0p3  noneswapsw  0   0
/dev/da1p1  /mnt/USBBD  ufs rw  2   2

And was able to mount by issuing command:
mount /mnt/USBBD



On Sep 29, 2016, at 8:39 AM, Shawn Bakhtiar 
<shashan...@hotmail.com<mailto:shashan...@hotmail.com>> wrote:

Good morning,

I followed the instructions here 
https://www.freebsd.org/doc/handbook/usb-disks.html to mount a Western Digital 
8TB USB drive, which (using auto mount) created the mount point /media/da1p1 
but when cd into the directory and do an 'ls' it takes a long time returning 
total 0, and when I try something like 'touch t' I get and an 'Input/output 
error'. dmesg output below. I actually don't need to auto mount I need to mount 
the drive at boot so I simply want to add it to my fstab, I was just testing 
the auto mount features for fun.

When I try to do it manually i get:
root@correo:/ # mount -t msdosfs /dev/da1p1 /media/USBBackupDrive
mount_msdosfs: /dev/da1p1: Invalid argument

same with:
root@correo:/ # mount /dev/da1p1 /media/USBBackupDrive
mount: /dev/da1p1: Invalid argument

Any help would be greatly appreciated,
Shawn


dmesg output:
ciss0: *** Surface Analysis Pass Information, LDrv=0 Number of passes=3139
ciss0: *** Surface Analysis Pass Information, LDrv=0 Number of passes=3140
ciss0: *** Surface Analysis Pass Information, LDrv=0 Number of passes=3141
ugen0.6:  at usbus0
umass0:  on 
usbus0
umass0:  SCSI over Bulk-Only; quirks = 0x8000
umass0:2:0:-1: Attached to scbus2
da1 at umass-sim0 bus 0 scbus2 target 0 lun 0
da1:  Fixed Direct Access SPC-4 SCSI device
da1: Serial Number 564B4A4D44554758
da1: 400.000MB/s transfers
da1: 7630885MB (15628052480 512 byte sectors: 255H 63S/T 972801C)
da1: quirks=0x2
ses0 at umass-sim0 bus 0 scbus2 target 0 lun 1
ses0:  Fixed Enclosure Services SPC-4 SCSI device
ses0: Serial Number 564B4A4D44554758
ses0: 400.000MB/s transfers
ses0: SCSI-3 ENC Device
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /medi

Error with auto mount

[Shawn Bakhtiar]

Good morning,

I followed the instructions here 
https://www.freebsd.org/doc/handbook/usb-disks.html to mount a Western Digital 
8TB USB drive, which (using auto mount) created the mount point /media/da1p1 
but when cd into the directory and do an 'ls' it takes a long time returning 
total 0, and when I try something like 'touch t' I get and an 'Input/output 
error'. dmesg output below. I actually don't need to auto mount I need to mount 
the drive at boot so I simply want to add it to my fstab, I was just testing 
the auto mount features for fun.

When I try to do it manually i get:
root@correo:/ # mount -t msdosfs /dev/da1p1 /media/USBBackupDrive
mount_msdosfs: /dev/da1p1: Invalid argument

same with:
root@correo:/ # mount /dev/da1p1 /media/USBBackupDrive
mount: /dev/da1p1: Invalid argument

Any help would be greatly appreciated,
Shawn


dmesg output:
ciss0: *** Surface Analysis Pass Information, LDrv=0 Number of passes=3139
ciss0: *** Surface Analysis Pass Information, LDrv=0 Number of passes=3140
ciss0: *** Surface Analysis Pass Information, LDrv=0 Number of passes=3141
ugen0.6:  at usbus0
umass0:  on 
usbus0
umass0:  SCSI over Bulk-Only; quirks = 0x8000
umass0:2:0:-1: Attached to scbus2
da1 at umass-sim0 bus 0 scbus2 target 0 lun 0
da1:  Fixed Direct Access SPC-4 SCSI device
da1: Serial Number 564B4A4D44554758
da1: 400.000MB/s transfers
da1: 7630885MB (15628052480 512 byte sectors: 255H 63S/T 972801C)
da1: quirks=0x2
ses0 at umass-sim0 bus 0 scbus2 target 0 lun 1
ses0:  Fixed Enclosure Services SPC-4 SCSI device
ses0: Serial Number 564B4A4D44554758
ses0: 400.000MB/s transfers
ses0: SCSI-3 ENC Device
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5
WARNING: autofs_trigger_one: request for /media/da1p1/ completed with error 5

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problem with nsswitch.conf

[Shawn Bakhtiar]

Oh Jesus!!! Thank you.. that worked.. obviously...

> On Sep 21, 2016, at 10:28 AM, Eric van Gyzen <vangy...@freebsd.org> wrote:
> 
> On 09/21/2016 12:21, Shawn Bakhtiar wrote:
>> Good morning All,
>> 
>> I'm trying to configure my server as an LDAP client. I installed the nslcd 
>> service and it's working great.
>> 
>> My problem is when I issue the command getent passwd it only returns the 
>> LDAP user not the local users. 
>> 
>> #
>> # nsswitch.conf(5) - name service switch configuration file
>> # $FreeBSD: releng/10.2/etc/nsswitch.conf 224765 2011-08-10 20:52:02Z dougb $
>> #
>> group: file ldap
>> group_compat: nis ldap
>> hosts: files dns
>> networks: files
>> passwd: file ldap
>> passwd_compat: nis ldap
>> shells: files 
>> services: files 
>> services_compat: nis
>> protocols: files 
>> rpc: files
>> 
>> 
>> When I change the above group and passwd setting back to compat (which was 
>> the default configuration) I get the local users but none of the ldap users 
>> show up. In fact nslcd is not even called (i've checked by running it in 
>> debug mode). So how do I configure nsswitch to use both the local 
>> /etc/passwd file and the ldap. I need this because without it services will 
>> not start. IE nslcd complains that nslcd is not a valid user when using the 
>> above configuration.
> 
> It should be "files", plural.
> 
> Eric

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem with nsswitch.conf

[Shawn Bakhtiar]

Good morning All,

I'm trying to configure my server as an LDAP client. I installed the nslcd 
service and it's working great.

My problem is when I issue the command getent passwd it only returns the LDAP 
user not the local users. 

#
# nsswitch.conf(5) - name service switch configuration file
# $FreeBSD: releng/10.2/etc/nsswitch.conf 224765 2011-08-10 20:52:02Z dougb $
#
group: file ldap
group_compat: nis ldap
hosts: files dns
networks: files
passwd: file ldap
passwd_compat: nis ldap
shells: files 
services: files 
services_compat: nis
protocols: files 
rpc: files


When I change the above group and passwd setting back to compat (which was the 
default configuration) I get the local users but none of the ldap users show 
up. In fact nslcd is not even called (i've checked by running it in debug 
mode). So how do I configure nsswitch to use both the local /etc/passwd file 
and the ldap. I need this because without it services will not start. IE nslcd 
complains that nslcd is not a valid user when using the above configuration.

Any help would greatly be appreciated,
Shawn

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Postfix and tcpwrappers?

[Shawn Bakhtiar]

On Jul 25, 2016, at 10:32 AM, Karl Denninger 
> wrote:

On 7/25/2016 12:04, Ronald Klop wrote:
On Mon, 25 Jul 2016 18:48:25 +0200, Karl Denninger
> wrote:

This may not belong in "stable", but since Postfix is one of the
high-performance alternatives to sendmail

Question is this -- I have sshguard protecting connections inbound, but
Postfix appears to be ignoring it, which implies that it is not paying
attention to the hosts.allow file (and the wrapper that enables it.)

Recently a large body of clowncars have been targeting my sasl-enabled
https gateway (which I use for client machines and thus do in fact need)
and while sshguard picks up the attacks and tries to ban them, postfix
is ignoring the entries it makes which implies it is not linked with the
tcp wrappers.

A quick look at the config for postfix doesn't disclose an obvious
configuration solutiondid I miss it?


Don't know if postfix can handle tcp wrappers, but I use bruteblock
[1] for protecting connections via the ipfw firewall. I use this for
ssh and postfix.

I recompiled sshguard to use ipfw and stuck the table lookup in my
firewall config. works, and is software-agnostic (thus doesn't care
if something was linked against tcpwrappers or not.)


I would triple concur with the above advice. using ipfw is a much better choice 
(especially at high volume) as ipfw works primarily at layer 3 (and in the 
kernel itself), Where as tcp wrappers works at layer 7 (requiring application 
awareness).

Here are the handbook references:
https://www.freebsd.org/doc/handbook/tcpwrappers.html
https://www.freebsd.org/doc/handbook/firewalls-ipfw.html


--
Karl Denninger
k...@denninger.net 
/The Market Ticker/
/[S/MIME encrypted email preferred]/

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"