USB Flash Drive in Stock
Hi, Glad to hear that you're on the market for usb driver memory, we are experienced in this field for about 8 years. There is much experience in usb driver memory with higher quality. What’s more, we have our own RD to meet any of your requirements. There are usb driver memory in stock and the quotation as follows: 1GB: EXW US$2.10, 2GB: EXW US$2.42, 4GB: EXW US$2.91, 8GB: EXW US$3.55, 16GB: EXW US$6.13, 32GB: EXW US$10.49, 64GB: EXW US$ 22.26, 128GB: EXW US$ 25.49, 256GB: EXW US$30.33 M.O.Q: 500PCS Please contact us without any hesitation if there is anything we can do for you. Look forward to hearing from you and establishing friendly business relationship between us. Best Regards. Jane2 attachment: USB_Flash_Drive.jpg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
USB host controllers on a server that does not use USB devices?
This is on an ia64 server. Do I need these devices in kernel: device ehci# EHCI host controller device ohci# OHCI PCI-USB interface device uhci# UHCI PCI-USB interface if I don't ever attach any usb devices to it? Thanks Anton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: configure recursively and build question
2013. március 19. 23:32 napon kalth...@googlemail.com írta: On Tue, Mar 12, 2013 at 05:45:07PM +0100, Istvan Gabor wrote: Hello: As there are no compiled FreeBSD 9.1 packages for pkg_tools I decided to build them. Last I started to build kde3. First I issued make configure-recursive in /usr/ports/x11/kde3, then make install clean, and left the computer for overnight to work. I expected a successful build by the morning but instead I found a screen requiring some config options (for apache). I selected the options and the build went on. But later other config windows came up, so far for mysqlclient, sane-backends, tk, tcl, libxine and sdl. So my question are: What is configure-recursive good for then? I thought it is for preventing interactions during the build process. Ho can I really configure everything in one step and leave the computer alone? Second, after I've done a configure-recursive, how can I start it over from scratch in case I want to change some config option? If I reissue make configure-recursive, I get only no configuration needed messages. Thanks, Istvan make config-recursive seems to be buggy. It seems not to be recursive as this would mean that with every change of an option of the root port or it's dependencies dependencies of the root port might change. This could mean that make config needs to be invoked for a port that wasn't in the inital dependecy list of root port. The root of all evil seems to be in /usr/ports/Mk/bsd.port.mk line 6187 ff. You might want to use ports-mgmt/portmaster. It creates options-files of a port and it's dependencies in a better way before starting to compile ports. OK. Thanks for the explanation and suggestion. Istvan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: w and who don't list users in FreeBSD 9.0 and 9.1
2013. március 19. 17:12 napon Ralf Mardorf ralf.mard...@rocketmail.com írta: On Tue, 2013-03-19 at 16:59 +0100, Istvan Gabor wrote: I tried google search but w and who are not good search terms. Indeed, it for sure isn't easy, but did you try with quotes and other options? http://lmgtfy.com/?q=freebsd+%22who+command%22 I don't know if there is a solution, but you're at least not the first who experienced this issue. Thank you. I tried this type of search before my posting but the results I looked at were not relevant or did not give a solution. I did not know about let me google that for you, thanks for that. Istvan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: w and who don't list users in FreeBSD 9.0 and 9.1
2013. március 19. 17:03 napon Ruben de Groot mai...@bzerk.org írta: On Tue, Mar 19, 2013 at 04:59:56PM +0100, Istvan Gabor typed: Hello: I have both FreeBSD 9.0 and 9.1 on two different computers. w and who commands do not list logged in users in any of them (either for root or a regular user). The output of w is: root@:/root # w 4:56PM up 10 mins, 0 users, load averages: 0.18, 0.26, 0.20 USER TTY FROM LOGIN@ IDLE WHAT root@:/root # And the output of who: root@:/root # who root@:/root # Why is this and how can I fix it? This can happen if your kernel and world are out of sync. 1. How could I check this? 2. I found that users are reported if they are logged in on terminal session or through ssh. User who is logged in through KDM3 into KDE3 session is not shown. Does this change the above diagnosis? Can it be something else, maybe? Thanks, Istvan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: w and who don't list users in FreeBSD 9.0 and 9.1
2013. március 19. 18:44 napon Nikos Vassiliadis nv...@gmx.com írta: On 19/3/2013 6:03 μμ, Ruben de Groot wrote: On Tue, Mar 19, 2013 at 04:59:56PM +0100, Istvan Gabor typed: Hello: I have both FreeBSD 9.0 and 9.1 on two different computers. w and who commands do not list logged in users in any of them (either for root or a regular user). The output of w is: root@:/root # w 4:56PM up 10 mins, 0 users, load averages: 0.18, 0.26, 0.20 USER TTY FROM LOGIN@ IDLE WHAT root@:/root # And the output of who: root@:/root # who root@:/root # Why is this and how can I fix it? This can happen if your kernel and world are out of sync. It can also happen if /var/run/utx.active is corrupt. Could you try deleting it? It will be re-created after a successful login. I tried this but did not make any change. Maybe the problem is related to the session type, KDE3. See my answer to Ruben. Thanks, Istvan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dumb down a Netgear Smart Switch
Em Ter, 2013-03-19 às 17:09 -1000, Al Plant escreveu: Aloha, Anybody on our list who can tell me how to set a Netgear GS108T 8 Port Smart Switch (Gigabit) to pass thru to a modem under FreeBSD. I have 2 other (non Smart) ones working with FreeBSD just fine in my rack and need to have the new one connect with a DSL modem on a static address. The instructions they sent me along with the switch that was a replacement for a non smart one at no charge is the type for using a DHCP service on Microsoft. (I cant complain about the up grade but its over kill for my purpose. Any help would be appreciated. Hello, My experience with smart switches is at minimum not good they sometimes block, they need programming, I had an experience with a dell smart switch that blocks the entire network of servers when a set of diskless stations boots, the only solution is to make it dumber. finally we changed that one for about 3 cisco gigabit 48 ports dumb switches and never ever heard about network problems again... Sergio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 8.1 install on Intel Romley platform
Dear Sir/Madam, We are facing a problem to install FreeBSD8.1 on Intel Romley platform, SAS HDD could not be detected. While we tried FreeBSD 9.1, it has no problem. However, our Firewall application only work on FreeBSD 8.1 and 8.3. Is there any driver or kernel update that we can integrate to let FreeBSD 8.1 install successfully? Best Regards, Belle Kuo Product Management Wiwynn Corporation Address: 8F, No. 90, Sec. 1, Xintai 5th Rd., Xizhi Dist., New Taipei City 22102, Taiwan Direct: +886 2-6612-3010 Mobile: +886 933 667688 Facsimile: +886 2 6615-8999 Email: belle_...@wiwynn.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fetchmail/sendmail: Domain of sender address does not exist
Anton Shterenlikht me...@bristol.ac.uk wrote: I sometimes see fetchmail complain: fetchmail: SMTP error: 553 5.1.8 ad...@system.mail... Domain of sender address ad...@system.mail does not exist Add FEATURE(accept_unresolvable_domains) to your sendmail configuration. -- Christian naddy Weisgerber na...@mips.inka.de ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: w and who don't list users in FreeBSD 9.0 and 9.1
Istvan Gabor suseuse...@lajt.hu writes: 2. I found that users are reported if they are logged in on terminal session or through ssh. User who is logged in through KDM3 into KDE3 session is not shown. Does this change the above diagnosis? Can it be something else, maybe? Well, if they don't start a login shell, they're not going to show up as logged in. Most terminal programs have an option to start them as login shells, but I don't know KDE well enough to know what the normal practice there would be. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dumb down a Netgear Smart Switch
On Wed, 20 Mar 2013, Sergio de Almeida Lenzi wrote: Em Ter, 2013-03-19 às 17:09 -1000, Al Plant escreveu: Aloha, Anybody on our list who can tell me how to set a Netgear GS108T 8 Port Smart Switch (Gigabit) to pass thru to a modem under FreeBSD. I have 2 other (non Smart) ones working with FreeBSD just fine in my rack and need to have the new one connect with a DSL modem on a static address. I have one of that model, and if you reset to factory defaults it should act as a dumb switch. There are some options that could be set that would interfere with operation (flow control, port negotiation, etc) but I am confident that none are set in the factory default configuration. (Stick a pin in the hole while power cycling). daniel feenberg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB host controllers on a server that does not use USB devices?
On 20 March 2013 05:10, Anton Shterenlikht me...@bristol.ac.uk wrote: This is on an ia64 server. Do I need these devices in kernel: device ehci# EHCI host controller device ohci# OHCI PCI-USB interface device uhci# UHCI PCI-USB interface if I don't ever attach any usb devices to it? Probably not on a server, but there are some built-in devices in some notebooks (webcam bluetooth) that are run through a usb bus. usbconfig(8) may be helpful. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 8.1 install on Intel Romley platform
On 03/20/13 12:44, belle_...@wiwynn.com wrote: We are facing a problem to install FreeBSD8.1 8.1 is not supported anymore; I don't think you'll get much help. our Firewall application only work on FreeBSD 8.1 and 8.3. 8.3 is still supported, so I'd move on to that one. SAS HDD could not be detected. While we tried FreeBSD 9.1, it has no problem. So, how does 9.1 detect it? However, Is there any driver or kernel update that we can integrate to let FreeBSD 8.1 install successfully? Perhaps you could post the dmesg at boot from 9.1. This could give the list some useful info. bye av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB host controllers on a server that does not use USB devices?
On 03/20/13 14:59, ill...@gmail.com wrote: Probably not on a server, but there are some built-in devices in some notebooks (webcam bluetooth) that are run through a usb bus. It happened to me to see an internal USB tape drive, connected to an USB port on the motherboard. bye av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Leaking disk space
Hi Guys,
We're seeing a problem with some of our FreeBSD/PostgreSQL servers
leaking quite significant amounts of disk space:
df -h /usr/local/pgsql/
Filesystem SizeUsed Avail Capacity Mounted on
/dev/mfid1s1d1.1T772G222G78%/usr/local/pgsql
du -sh /usr/local/pgsql/
741G/usr/local/pgsql/
Stopping Postgres doesn't fix it, but rebooting does which points at
the OS rather than PG to me. However, the leak is only apparent in the
dedicated pgsql partition, and only on our database servers, so
PostgreSQL seems to at least be involved. The partition itself is a
relatively standard UFS partition:
grep /usr/local/pgsql /etc/fstab
/dev/mfid1s1d /usr/local/pgsqlufs rw 2 2
tunefs -p /usr/local/pgsql/
tunefs: POSIX.1e ACLs: (-a)disabled
tunefs: NFSv4 ACLs: (-N) disabled
tunefs: MAC multilabel: (-l) disabled
tunefs: soft updates: (-n) enabled
tunefs: gjournal: (-J) disabled
tunefs: trim: (-t) disabled
tunefs: maximum blocks per file in a cylinder group: (-e) 2048
tunefs: average file size: (-f)16384
tunefs: average number of files in a directory: (-s) 64
tunefs: minimum percentage of free space: (-m) 8%
tunefs: optimization preference: (-o) time
tunefs: volume label: (-L)
LSOF isn't showing any open files:
lsof +L /usr/local/pgsql/ | awk '{ print $8 }' | grep 0 | wc -l
0
We're not creating filesystem snapshots:
find /usr/local/pgsql/ -flags snapshot
Not all of our servers are leaking space, it's only the more
recently-installed systems. Here's a quick breakdown of versions:
FreeBSD PostgreSQL Leaking?
8.0 8.4.4no
8.2 9.0.4no
8.3 9.1.4yes
8.3 9.2.3yes
9.1 9.2.3yes
Any ideas what's going on here, or where we could start debugging?
Thanks,
Dan
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Leaking disk space
On Wed, 20 Mar 2013 15:23:18 +
Dan Thomas godd...@gmail.com wrote:
Hi Guys,
We're seeing a problem with some of our FreeBSD/PostgreSQL servers
leaking quite significant amounts of disk space:
df -h /usr/local/pgsql/
Filesystem SizeUsed Avail Capacity Mounted on
/dev/mfid1s1d1.1T772G222G78%/usr/local/pgsql
du -sh /usr/local/pgsql/
741G/usr/local/pgsql/
Stopping Postgres doesn't fix it, but rebooting does which points at
the OS rather than PG to me. However, the leak is only apparent in the
dedicated pgsql partition, and only on our database servers, so
PostgreSQL seems to at least be involved. The partition itself is a
relatively standard UFS partition:
grep /usr/local/pgsql /etc/fstab
/dev/mfid1s1d /usr/local/pgsqlufs rw 2 2
tunefs -p /usr/local/pgsql/
tunefs: POSIX.1e ACLs: (-a)disabled
tunefs: NFSv4 ACLs: (-N) disabled
tunefs: MAC multilabel: (-l) disabled
tunefs: soft updates: (-n) enabled
tunefs: gjournal: (-J) disabled
tunefs: trim: (-t) disabled
tunefs: maximum blocks per file in a cylinder group: (-e) 2048
tunefs: average file size: (-f)16384
tunefs: average number of files in a directory: (-s) 64
tunefs: minimum percentage of free space: (-m) 8%
tunefs: optimization preference: (-o) time
tunefs: volume label: (-L)
LSOF isn't showing any open files:
lsof +L /usr/local/pgsql/ | awk '{ print $8 }' | grep 0 | wc -l
0
We're not creating filesystem snapshots:
find /usr/local/pgsql/ -flags snapshot
Not all of our servers are leaking space, it's only the more
recently-installed systems. Here's a quick breakdown of versions:
FreeBSD PostgreSQL Leaking?
8.0 8.4.4no
8.2 9.0.4no
8.3 9.1.4yes
8.3 9.2.3yes
9.1 9.2.3yes
Any ideas what's going on here, or where we could start debugging?
Somethings to check:
a) Where do you have the wal files?
b) Are you sure that unused/old wal files are erased?
c) Do you have any postgres log level activated (like the ones used for long
queries)?
d) Does your queries have GROUP BY on very big data sets? Those create big
temporal data files.
e) With question a) and b), do you use streaming replication?
Thanks,
Dan
--- ---
Eduardo Morras emorr...@yahoo.es
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Leaking disk space
On 20/03/2013 15:23, Dan Thomas wrote: Hi Guys, We're seeing a problem with some of our FreeBSD/PostgreSQL servers leaking quite significant amounts of disk space: df -h /usr/local/pgsql/ Filesystem SizeUsed Avail Capacity Mounted on /dev/mfid1s1d1.1T772G222G78%/usr/local/pgsql du -sh /usr/local/pgsql/ 741G/usr/local/pgsql/ Stopping Postgres doesn't fix it, but rebooting does which points at the OS rather than PG to me. However, the leak is only apparent in the dedicated pgsql partition, and only on our database servers, so PostgreSQL seems to at least be involved. The partition itself is a relatively standard UFS partition: Hi, Dan You're not the first person to report that. Please see the thread: leaking lots of unreferenced inodes (pg_xlog files?), maybe after moving tables and indexes to tablespace on different volume on the freebsd...@freebsd.org mailing list. Kirk McKusick was investigating the original report: CC'd. Cheers, Matthew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Leaking disk space
a) Where do you have the wal files?
pg_xlog is symlinked to /usr/local/pglog/pg_xlog (ie, out of the
partition mounted as /usr/local/pgsql which is exhibiting this
behaviour).
b) Are you sure that unused/old wal files are erased?
As above, but yes they seem to be being deleted properly
c) Do you have any postgres log level activated (like the ones used
for long queries)?
Yes we have slow query logging enabled. pg_log is symlinked out of
that partition to /usr/local/pglog/pg_log as well.
d) Does your queries have GROUP BY on very big data sets? Those create
big temporal data files.
Yes we do a lot of that! However there are definitely no unlinked
files, and the problem doesn't go away when pg is shut down. However a
reboot does fix it.
e) With question a) and b), do you use streaming replication?
Yes we do. This problem is not present on the warm standby servers
that are being streamed to. We have failed over to the warm standbys
previously (we're currently doing this regularly to work around the
problem without too much downtime). Once we switch the warm standby to
primary, it begins leaking space.
On 20 March 2013 16:02, Eduardo Morras emorr...@yahoo.es wrote:
On Wed, 20 Mar 2013 15:23:18 +
Dan Thomas godd...@gmail.com wrote:
Hi Guys,
We're seeing a problem with some of our FreeBSD/PostgreSQL servers
leaking quite significant amounts of disk space:
df -h /usr/local/pgsql/
Filesystem SizeUsed Avail Capacity Mounted on
/dev/mfid1s1d1.1T772G222G78%/usr/local/pgsql
du -sh /usr/local/pgsql/
741G/usr/local/pgsql/
Stopping Postgres doesn't fix it, but rebooting does which points at
the OS rather than PG to me. However, the leak is only apparent in the
dedicated pgsql partition, and only on our database servers, so
PostgreSQL seems to at least be involved. The partition itself is a
relatively standard UFS partition:
grep /usr/local/pgsql /etc/fstab
/dev/mfid1s1d /usr/local/pgsqlufs rw 2 2
tunefs -p /usr/local/pgsql/
tunefs: POSIX.1e ACLs: (-a)disabled
tunefs: NFSv4 ACLs: (-N) disabled
tunefs: MAC multilabel: (-l) disabled
tunefs: soft updates: (-n) enabled
tunefs: gjournal: (-J) disabled
tunefs: trim: (-t) disabled
tunefs: maximum blocks per file in a cylinder group: (-e) 2048
tunefs: average file size: (-f)16384
tunefs: average number of files in a directory: (-s) 64
tunefs: minimum percentage of free space: (-m) 8%
tunefs: optimization preference: (-o) time
tunefs: volume label: (-L)
LSOF isn't showing any open files:
lsof +L /usr/local/pgsql/ | awk '{ print $8 }' | grep 0 | wc -l
0
We're not creating filesystem snapshots:
find /usr/local/pgsql/ -flags snapshot
Not all of our servers are leaking space, it's only the more
recently-installed systems. Here's a quick breakdown of versions:
FreeBSD PostgreSQL Leaking?
8.0 8.4.4no
8.2 9.0.4no
8.3 9.1.4yes
8.3 9.2.3yes
9.1 9.2.3yes
Any ideas what's going on here, or where we could start debugging?
Somethings to check:
a) Where do you have the wal files?
b) Are you sure that unused/old wal files are erased?
c) Do you have any postgres log level activated (like the ones used for long
queries)?
d) Does your queries have GROUP BY on very big data sets? Those create big
temporal data files.
e) With question a) and b), do you use streaming replication?
Thanks,
Dan
--- ---
Eduardo Morras emorr...@yahoo.es
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
getopt port in FreeBSD-9.1
Hello: I would like to install firefox-esr-i18n port but is stops at getopt install. I tried to install getopt port but it gives: root@:/usr/ports/misc/getopt # make install clean === Extracting for getopt-1.1.5 = SHA256 Checksum mismatch for getopt-1.1.5.tar.gz. === Refetch for 1 more times files: getopt-1.1.5.tar.gz = getopt-1.1.5.tar.gz doesn't seem to exist in /usr/ports/distfiles/. = Attempting to fetch http://software.frodo.looijaard.name/getopt/files/getopt-1.1.5.tar.gz fetch: http://software.frodo.looijaard.name/getopt/files/getopt-1.1.5.tar.gz: Connection refused = Attempting to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/getopt-1.1.5.tar.gz fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/getopt-1.1.5.tar.gz: File unavailable (e.g., file not found, no access) = Couldn't fetch it - please try to retrieve this = port manually into /usr/ports/distfiles/ and try again. *** [do-fetch] Error code 1 Stop in /usr/ports/misc/getopt. *** [checksum] Error code 1 Stop in /usr/ports/misc/getopt. The getopt which has the checksum mismatch is from http://software.frodo.looijaard.name/getopt/files/getopt-1.1.5.tar.gz downloaded manually by browser and copied into /usr/ports/distfiles. I tried to download manually ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/getopt-1.1.5.tar.gz but my browser can't find it either. That directory has getopt-1.1.4.tar.gz How to solve this? Thanks, Istvan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: IPC Shared memory segment
The solution was given at revision 233760. Link for description: http://svnweb.freebsd.org/base?view=revisionrevision=233760 Thanks to all! -- Respectfully, Stanislav Putrya System administrator FotoStrana.Ru Ltd. ICQ IM: 328585847 Jabber-GoogleTalk: root.vagner mob.phone SPB: +79215788755 mob.phone RND: +79525600664 email: vag...@bsdway.ru email: put...@playform.ru email: root.vag...@gmail.com site: bsdway.ru site: fotostrana.ru ( ) ASCII ribbon campaign X - against HTML, vCards and / \ - proprietary attachments in e-mail ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Current Way To Update Sources Rebuild World/Kernel? -- SOLVED
On Tue, 19 Mar 2013 14:06:41 -0700, Drew Tomlinson wrote: Thanks for the replies. Using freebsd-update seemed the simplest method since it was already included. Worked just fine for getting the sources. Probably in the future there will be a csup-equivalent included with the OS, plus configuration templates that can be used to do a source incorporation via SVN. And following the steps listed in comments in /usr/src/Makefile worked for building and installing the sources. I've relied on them for many years, and they seem to work happily. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ports issue: delete upstream perl dependencies by mistake
I did something dumb I think with ports on my box. In the process of upgrading Perl, for every package that depended on Perl, via pkgdb, I somehow managed to delete the fact that the package depends on Perl itself. So now I have a bunch of packages that no longer reference Perl in it's upstream dependency listing. e.g. $ pkg_info -R p5-Mail-SpamAssassin-3.3.2_8 Information for p5-Mail-SpamAssassin-3.3.2_8: $ How can I fix this? Short of deleting all the packages (which I don't even know all they are, except for the p5-ones) and rebuilding? Thanks in advance, Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Leaking disk space
On 21/03/2013 3:55 AM, Dan Thomas wrote: Stopping Postgres doesn't fix it, but rebooting does which points at Have you used fstat to identify the big growing file which is taking up the space, and which process has the file open? A file which has been unlinked from all directories won't be seen by du, but it does not free disk space until no process has it open. USER CMD PID FD MOUNT INUM MODE SZ|DV R/W root syslogd476488 /4317027 -rw-r--r-- 19776 w root syslogd476489 /4317041 -rw--- 63 w That might help to track it down. Danny ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ZFS question
I'm experiencing fatal issues with pools hanging my machine requiring a hard-reset. I'm new to freebsd and these mailing lists in particular, is this the place to ask for help? __ it has a certain smooth-brained appeal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS question
Several people, including me, have an issue like this with 9.1. Your best bet is to try 9.0. On Wed, Mar 20, 2013 at 5:49 PM, Quartz qua...@sneakertech.com wrote: I'm experiencing fatal issues with pools hanging my machine requiring a hard-reset. I'm new to freebsd and these mailing lists in particular, is this the place to ask for help? __ it has a certain smooth-brained appeal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Reed A. Cartwright, PhD Assistant Professor of Genomics, Evolution, and Bioinformatics School of Life Sciences Center for Evolutionary Medicine and Informatics The Biodesign Institute Arizona State University ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS question
Several people, including me, have an issue like this with 9.1. Your best bet is to try 9.0. Hmm... interesting. Is there any consensus as to what's going on? Before anyone jumps to conclusions though, lemme just post the whole issue so we're on the same page (apologizes if it turns out this isn't the right mailing list for this): I have a raidz2 comprised of six sata drives connected via my motherboard's intel southbridge sata ports. All of the bios raid options are disabled and the drives are in straight ahci mode (hotswap enabled). The system (accounts, home dir, etc) is installed on a separate 7th drive formatted as normal ufs, connected to a separate non-intel motherboard port. As part of my initial stress testing, I'm simulating failures by popping the sata cable to various drives in the 6x pool. If I pop two drives, the pool goes into 'degraded' mode and everything works as expected. I can zero and replace the drives, etc, no problem. However, when I pop a third drive, the machine becomes VERY unstable. I can nose around the boot drive just fine, but anything involving i/o that so much as sneezes in the general direction of the pool hangs the machine. Once this happens I can log in via ssh, but that's pretty much it. I've reinstalled and tested this over a dozen times, and it's perfectly repeatable: `ls` the dir where the pool is mounted? hang. I'm already in the dir, and try to `cd` back to my home dir? hang. zpool destroy? hang. zpool replace? hang. zpool history? hang. shutdown -r now? gets halfway through, then hang. reboot -q? same as shutdown. The machine never recovers (at least, not inside 35 minutes, which is the most I'm willing to wait). Reconnecting the drives has no effect. My only option is to hard reset the machine with the front panel button. Googling for info suggested I try changing the pool's failmode setting from wait to continue, but that doesn't appear to make any difference. For reference, this is a virgin 9.1-release installed off the dvd image with no ports or packages or any extra anything. I don't think I'm doing anything wrong procedure wise. I fully understand and accept that a raidz2 with three dead drives is toast, but I will NOT accept having it take down the rest of the machine with it. As it stands, I can't even reliably look at what state the pool is in. I can't even nuke the pool and start over without taking the whole machine offline. __ it has a certain smooth-brained appeal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS question
(Please keep me CC'd as I'm not subscribed to -questions) Lots to say about this. 1. freebsd-fs is the proper list for filesystem-oriented questions of this sort, especially for ZFS. 2. The issue you've described is experienced by some, and **not** experienced by even more/just as many, so please keep that in mind. Each/every person's situation/environment/issue has to be treated separately/as unique. 3. You haven't provided any useful details, even in your follow-up post here: http://lists.freebsd.org/pipermail/freebsd-questions/2013-March/249958.html All you've provided is a general overview with no technical details, no actual data. You need to provide that data verbatim. You need to provide: - Contents of /boot/loader.conf - Contents of /etc/sysctl.conf - Output from zpool status - Output from zpool get all - Output from zfs get all - Output from dmesg (probably the most important) - Output from sysctl vfs.zfs kstat.zfs I particularly tend to assist with disk-level problems, so if this turns out to be a disk-level issue (and NOT a controller or controller driver issue), I can help quite a bit with that. 4. I would **not** suggest rolling back to 9.0. This recommendation is solves nothing -- if there is truly a bug/livelock issue, then that needs to be tracked down. By rolling back, if there is an issue, you're effectively ensuring it'll never get investigated or fixed, which means you can probably expect to see this in 9.2, 9.3, or even 10.x onward. If you can't deal with the instability, or don't have the time/cycles/interest to help track it down, that's perfectly okay too: my recommendation is to go back to UFS (there's no shame in that). Else, as always, I strongly recommend running stable/9 (keep reading). 5. stable/9 (a.k.a. FreeBSD 9.1-STABLE) just recently (~5 days ago) MFC'd an Illumos ZFS feature solely to help debug/troubleshoot this exact type of situation: introduction of the ZFS deadmean thread. Reference materials for what that is: http://svnweb.freebsd.org/base?view=revisionrevision=248369 http://svnweb.freebsd.org/base?view=revisionrevision=247265 https://www.illumos.org/issues/3246 The purpose of this feature (enabled by default) is to induce a kernel panic when ZFS I/O stalls/hangs for unexpectedly long periods of time (configurable via vfs.zfs.deadman_synctime). Once the panic happens (assuming your system is configured with a slice dedicated to swap (ZFS-backed swap = bad bad bad) and use of dumpdev=auto in rc.conf), upon reboot the system should extract the crash dump from swap and save it into /var/crash. At that point kernel developers on the -fs list can help tell you *exactly* what to do with kgdb(1) that can shed some light on what happened/where the issue may lie. All that's assuming that the issue truly is ZFS waiting for I/O and not something else (like ZFS internally spinning hard in its own code). Good luck, and let us know how you want to proceed. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS question
Note that my issue seems to do with an interaction between the CAM system and the MPS driver in 9.1. Thus it is more than likely different than what you are experiencing Quartz. Now that ZFS deadman has been incorporated into stable, I'll probably give a 9.1 (i.e. 9/stable) another try. Jeremy, I have a question about enabling kernel dumps based on my current swap config. I currently have a 1TB drive split into 4 geli encrypted swap partitions (Freebsd doesn't like swap partitions over ~250 GB and I have lots of RAM). These partitions are UFS-swap partitions and are not backed by any mirroing or ZFSing. So, how do I best enable crash dumps? If I need to remove encryption, I can do that. On Wed, Mar 20, 2013 at 9:45 PM, Jeremy Chadwick j...@koitsu.org wrote: (Please keep me CC'd as I'm not subscribed to -questions) Lots to say about this. 1. freebsd-fs is the proper list for filesystem-oriented questions of this sort, especially for ZFS. 2. The issue you've described is experienced by some, and **not** experienced by even more/just as many, so please keep that in mind. Each/every person's situation/environment/issue has to be treated separately/as unique. 3. You haven't provided any useful details, even in your follow-up post here: http://lists.freebsd.org/pipermail/freebsd-questions/2013-March/249958.html All you've provided is a general overview with no technical details, no actual data. You need to provide that data verbatim. You need to provide: - Contents of /boot/loader.conf - Contents of /etc/sysctl.conf - Output from zpool status - Output from zpool get all - Output from zfs get all - Output from dmesg (probably the most important) - Output from sysctl vfs.zfs kstat.zfs I particularly tend to assist with disk-level problems, so if this turns out to be a disk-level issue (and NOT a controller or controller driver issue), I can help quite a bit with that. 4. I would **not** suggest rolling back to 9.0. This recommendation is solves nothing -- if there is truly a bug/livelock issue, then that needs to be tracked down. By rolling back, if there is an issue, you're effectively ensuring it'll never get investigated or fixed, which means you can probably expect to see this in 9.2, 9.3, or even 10.x onward. If you can't deal with the instability, or don't have the time/cycles/interest to help track it down, that's perfectly okay too: my recommendation is to go back to UFS (there's no shame in that). Else, as always, I strongly recommend running stable/9 (keep reading). 5. stable/9 (a.k.a. FreeBSD 9.1-STABLE) just recently (~5 days ago) MFC'd an Illumos ZFS feature solely to help debug/troubleshoot this exact type of situation: introduction of the ZFS deadmean thread. Reference materials for what that is: http://svnweb.freebsd.org/base?view=revisionrevision=248369 http://svnweb.freebsd.org/base?view=revisionrevision=247265 https://www.illumos.org/issues/3246 The purpose of this feature (enabled by default) is to induce a kernel panic when ZFS I/O stalls/hangs for unexpectedly long periods of time (configurable via vfs.zfs.deadman_synctime). Once the panic happens (assuming your system is configured with a slice dedicated to swap (ZFS-backed swap = bad bad bad) and use of dumpdev=auto in rc.conf), upon reboot the system should extract the crash dump from swap and save it into /var/crash. At that point kernel developers on the -fs list can help tell you *exactly* what to do with kgdb(1) that can shed some light on what happened/where the issue may lie. All that's assuming that the issue truly is ZFS waiting for I/O and not something else (like ZFS internally spinning hard in its own code). Good luck, and let us know how you want to proceed. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Reed A. Cartwright, PhD Assistant Professor of Genomics, Evolution, and Bioinformatics School of Life Sciences Center for Evolutionary Medicine and Informatics The Biodesign Institute Arizona State University ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS question
1. freebsd-fs is the proper list for filesystem-oriented questions of
this sort, especially for ZFS.
Ok, I'm assuming I should subscribe to that list and post there then?
2. The issue you've described is experienced by some, and **not**
experienced by even more/just as many, so please keep that in mind.
Well, that's a given. Presumably if zfs was flat out totally broken, 9.x
wouldn't have been released or I would've already found a million pages
about this via google. I'm assuming my problem is a corner case and
there might've been a bug/regression, or I fundamentally don't
understand how this works.
3. You haven't provided any useful details, even in your follow-up post
here:
I got the impression that there wasn't a lot of overlap between the
mailing lists and the forums, so I wanted to post in both simultaneously.
- Contents of /boot/loader.conf
- Contents of /etc/sysctl.conf
- Output from zpool get all
- Output from zfs get all
- Output from sysctl vfs.zfs kstat.zfs
I'm running a *virgin* 9.1 with no installed software or modifications
of any kind (past setting up a non-root user). All of these will be at
their install defaults (with the possible exception of the failmode
setting, but that didn't help when I tried it the first time, so I
didn't bother during later re-installs).
- Output from zpool status
There isn't a lot of detail to be had here after I pop the 3rd
drive, zfs/zpool commands almost always cause the system to hang, so I'm
not sure if I can get anything out of them. Prior to the hang it will
just tell you I have a six-drive raidz2 with two of the drives
removed, so I'm not sure how that will be terribly useful.
I can tell you though that I'm creating the array with the following
command:
zpool create -f array raidz2 ada{2,3,4,5,6,7}
There are eight drives in the machine at the moment, and I'm not messing
with partitions yet because I don't want to complicate things. (I will
eventually be going that route though as the controller tends to
renumber drives in a first-come-first-serve order that makes some things
difficult).
- Output from dmesg (probably the most important)
When? ie; right after boot, or after I've hot plugged a few drives, or
yanked them, or created a pool, or what?
I particularly tend to assist with disk-level problems,
This machine is using a pile of spare seagate 250gb drives, if that
makes any difference.
By rolling back, if there is an issue, you're
effectively ensuring it'll never get investigated or fixed,
That's why I asked for clarification, to see if it was a known
regression in 9.1 or something similar.
or don't have the
time/cycles/interest to help track it down,
I have plenty of all that, for better or worse :)
that's perfectly okay too:
my recommendation is to go back to UFS (there's no shame in that).
At the risk of being flamed off the list, I'll switch to debian if it
comes to that. I use freebsd exclusively for zfs.
Else, as always, I strongly recommend running stable/9 (keep reading).
My problem with tracking -stable is the relative volatility. If I'm
trying to debug a problem it's not always easy or possible to keep
consistent/known versions of things. With -release I know exactly what
I'm getting and it cuts out a lot of variables.
just recently (~5 days ago)
MFC'd an Illumos ZFS feature solely to help debug/troubleshoot this
exact type of situation: introduction of the ZFS deadmean thread.
Yes, I already discovered this from various solaris threads I encountered.
The purpose of this feature (enabled by default) is to induce a kernel
panic when ZFS I/O stalls/hangs
This doesn't really help my situation though. If I wanted a panic I'd
just set failmode=panic.
All that's assuming that the issue truly is ZFS waiting for I/O and not
something else
Well, everything I've read so far indicates that zfs has issues when
dealing with un-writable pools, so I assume that's what's going on here.
__
it has a certain smooth-brained appeal
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
