Tag Info

Hot answers tagged

12

The -F switch comes in handy if you have messed with the destination dataset after it has been received. Once you do any changes to it (including doing something as innocent as a directory listing as this would change atimes), it is no longer in the state it was in after the initial transfer. Trying to run a plain zfs receive from an incremental data stream ...


11

FreeNAS is a NAS solution, as such, some technical choices are hidden behind whatever firmware, system or GUI such appliance can use. If you get the partition schema used on a given disk inside a ZFS pool made with FreeNAS (small VM example): $ glabel status Name Status Components ...


11

I think you should reconsider your use of FreeNAS. You've had an uncharacteristically. large. number. of issues. with. your. FreeNAS. installation(s). over. the years. Many of these issues were planning and ZFS design problems. It may be time to refactor or rebuild your environment now that you have some knowledge of best or better-practices.


8

Briefly... Linux is a kernel, FreeBSD is an Operating System. So you really can't compare them like you want. The major distributions of Linux each have various levels of compatibility and differences... but I'll try to hit the things you named at least: There are a couple different package managers (dpkg and rpm probably being the most popular) for Linux ...


6

No. If you refer to the FreeBSD handbook information on freebsd-update you will see, in a big gray box, the following note (emphasis added): Binary updates are available for all architectures and releases currently supported by the security team. Before updating to a new release, its release announcement should be reviewed as it contains important ...


6

You could reword this as a non-shopping question, "How do I hook up a dozen SATA drives without using port multipliers or multiple PCI cards?" so I'll write an answer to that magical question: Buy a multi-ported SAS card and associated SAS 4x breakout cable (SFF-8087 MiniSAS to 4 SATA). 6gbps SAS2 is like SATA3 (6Gbps). Then use whatever motherboard you ...


6

Your problem is not FreeBSD, it's Apache. Apache 2.4 has substantially different configuration file directives than Apache 2.2. You cannot just throw the 2.2 configuration file in place and start your 2.4 server using it - you will need to put important bits (like the SSL Certificate and Key files - per the error message you're getting) in place, and ...


5

You are thinking about things from the wrong level, is all. If you move a file within the confines of a single ZFS dataset, it will react similarly to what you're expecting. If you move a file within the confines of a pool, but between datasets, it is a real move. Yes, technically the data just went from point A to point B and both points are on the same ...


5

The number of files and directories involved in a zfs send/recv stream should have no direct impact on its transfer speed. Indirectly, it might, because it is usually true to say that the 'spread' of the dataset across your disks will be higher with more directories/files, depending on the workload that generated them. This matters, because it's far easier ...


4

Those messages are probably periodic reports. It's quite common to set daily_show_success=NO in /etc/periodic.conf so it doesn't generate "all's good" messages. Also, daily_output="$destination" should be set to your e-mail address or a log file that you can monitor. The same can be set for weekly_ and monthly_ - and probably should be. You can delete those ...


4

That should take care of that message for root logins. If you're logging in as another user, you'll need to add that to the ~/.bashrc of each user you want to disable it for. Or you can put it in the central startup file: /etc/profile to have it take effect for all users. You will need to check to see if MAILCHECK is being set at a later point in the ...


4

Should we add them to the existing zroot pool and allocate it. This seems like a bad idea since the original pool was designed to run as the root filesystem. First, zpools and zfs file systems are separate concepts (you can't actually separate them, but should when thinking about their setup). So pools are not "designed to run as the root filesystem", ...


4

First, FIX YOUR PORTS - rm -rf /usr/ports if that's what it takes. This will not harm installed software. Use portsnap for an easy way to grab a new copy of the ports tree. Advanced users can use svn. Second, DO NOT compile Apache from downloaded source. You're begging for trouble, and should NOT be surprised that you've found it. Use the ports tree. Even ...


4

Generally, you can consult the contents of the /usr/ports/UPDATING file on how to deal non-trivial upgrades. Usually, it provides solutions for users that are using portupgrade, portmaster or binary pkgng packages. Here are the instructions from the 20130612 entry in the UPDATING file: ... Please rebuild all Perl ports and all ports that depend on it: ...


4

The problem is that the clients didn't realise that the nfs server went away, so they're still trying to access the filehandle that was originally created the previous time they mounted the file system. Normally, rebooting the client is a sure way of making it remount the file systems. But if you don't want to do that, start by killing all processes that ...


3

It depends on your zpool arrangement, RAID type and whether you'll have any desire/ability to rewrite the data. If you're using ZFS in a group of RAIDZ vdevs, you can only expand by adding vdevs. New data will utilize the full set of drives, but existing data will not be redistributed. The same applies to zpool mirrors, but you can add those in smaller ...


3

This is tested on FreeBSD 10.0-RELEASE, but will likely work on FreeBSD 9.x. BIOS Configuration Open the BIOS settings and navigate to “Advanced → Serial Port Console Redirection” and ensure “SOL Console Redirection” is set to “Enabled” (you do not need to enable COM1 or COM2 or Out-of-Band management). Open the “SOL Console Redirection Settings” and ...


3

You can install annoy-o-tron monitoring software (like Tiger), or even copy the scripts from your FreeBSD system (/etc/periodic/{daily,weekly,monthly,security}/* and the periodic script itself in /usr/sbin) and modify/run them on your Debian box if you really want to, but this is a bad idea. The periodic emails on FreeBSD are a TERRIBLE monitoring solution ...


3

Run a regular script (cron) that checks zpool status -x output. Longer-term, the ZFS on Linux project is working towards this in the form of an event daemon. The Solaris-derived systems had access to the Fault Management Architecture. As far as automated reports, even commercial solutions like NexentaStor use scheduled checks. There's nothing wrong with ...


3

I would think the error message is pretty self explanatory: Packages are not yet suported. . . . therefore you must . . . Use pkg(8) directly. or alternatively don't specify -PP and upgrade wget via the port instead of trying to use the package...


3

You can disable remote logs adding the following line to the file '/etc/rc.conf'. syslogd_flags="-s" Or use this one to close the network sockets: syslogd_flags="-ss" After added the syslogd_flags you can use this command to restart the service: service syslogd restart


3

Blindly installing updates (even freebsd-update updates) can be a Bad Thing: One option in rc.conf changes, and suddenly your machine has no SSH daemon anymore. Similarly you probably don't want to blindly install all available port updates via portsnap / portupgrade -a -- you might take a major version number bump and break the universe, or you might ...


3

The "extra" options were deprecated by OpenBSD over 9 years ago and removed in pfctl revision 1.143 (Mar 23, 2010) with the following comments: remove -A, -O, -R and -T load the partial loading of a ruleset (leaving ancors aside) is wrong and conflicts with the general idea of how pf works. last not least it breaks with the optimizer generating ...


3

fsck -y will force fsck to "fix" the errors. Considering you have superblock, bit map, and summary errors the disk is likely fried or something truly horrible happened. In any case, backup whatever you can off the disk and consider reinstalling/reimaging. Looks like you're running a SATA disk. If you can get the system to boot you should check the SMART ...


3

As the next three words of the error message imply, the right thing to do is run fsck manually (which you're doing). fsck (usually run with -y so you don't have to manually say yes to all the prompts) will resolve the soft update inconsistencies and usually leave you with a working system again. (Exceptions exist where whatever caused the inconsistency has ...


3

To get a disk serial requires that it is running and available: camcontrol identify <device> |grep ^serial (this might be (S)ATA specific) smartcl -i <device> |grep ^Serial reading the disk label once removed from the enclosure In your case, I think the 3rd solution is the only available. So, Assuming you just want first identify the disk: ...


3

This is most likely because the file that used to be known as /var/log/messages is still open despite having been unlinked. Kill/restart the process that holds the file open (I would bet on syslogd) so that the space can be freed. Alternatively there could be more links to the file, but that seems rather unlikely unless you have deliberately set that up.


3

You'll probably want to check out /etc/devd.conf. devd is the primary way on FreeBSD of reacting to kernel/hardware events. There's an example in there that shows how to match a network UP/DOWN event and run a task, as below, and the man page has some good information. notify 0 { match "system" "IFNET"; match "type" "LINK_UP"; ...


3

CPU load information can be obtained in shell script from sysctl kern.cp_times. This is commulative counters, and to get load in % you need derivative, e. g. get kern.cp_times with 1 minute interval and divide counters by 60. But more easy to use existing monitoring systems like Nagios (there are many monitoring systems, but no perfect and I can't suggest ...


3

If you have the ports tree installed, just make install clean from /usr/ports/ports-mgmt/pkg. If you don't have ports: fetch "http://pkg.freebsd.org/freebsd:10:x86:64/latest/Latest/pkg.txz" setenv SIGNATURE_TYPE NONE pkg add pkg.txz If you're not using the default shell you might have to use set or export instead of setenv. And now to rant about ...



Only top voted, non community-wiki answers of a minimum length are eligible