Re: 'nodump' on directories: new contents still dumped
Bram Schoenmakers wrote: Op maandag 19 maart 2007, schreef Alex Zbyslaw: Hi, 1) There is a bug in whatever version of FreeBSD you are running and -h 1 is somehow *not* the default. 6.2 Release? It's a FreeBSD 4.10 (I know, I know, no need to tell me, we're going to migrate to something newer :) No preaching from me; I'm still on 5.4 which might be newer than yours but still obsolete :-) If you've covered any security issues, run what works for you! I've checked in the source code and on 5.4 and what I think to be 4.10 in the CVS Repository, there is clearly an assignment honorlevel = 1 which gets overridden by any -h flag, and I can't see any other assignments. Then a flag nonodump is set based on the honorlevel and dump level. That looks correct to me. My best guess is still some problem with your command line. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 'nodump' on directories: new contents still dumped
Bram Schoenmakers wrote: Op vrijdag 16 maart 2007, schreef Alex Zbyslaw: Can you try explicitly putting a -h 0 into your incremental command line and see if that makes a difference? I've done that and now dump behaves like it should. I don't understand why, because the man page says that -h 1 is default (and shouldn't be supplied then). But with -h 0 on every incremental dump it's OK now. I can only think of two possibilities: 1) There is a bug in whatever version of FreeBSD you are running and -h 1 is somehow *not* the default. 6.2 Release? 2) There is some kind of bug with your command line, but without seeing it, I can't tell. Glad you got the problem worked around; when I finally get around to 6.2 I will be curious to see if I can replicate the problem. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 'nodump' on directories: new contents still dumped
Op maandag 19 maart 2007, schreef Alex Zbyslaw: Hi, 1) There is a bug in whatever version of FreeBSD you are running and -h 1 is somehow *not* the default. 6.2 Release? It's a FreeBSD 4.10 (I know, I know, no need to tell me, we're going to migrate to something newer :) It's strange, since I've checked the CVS logs for dump(8) and couldn't find a commit which would have solved that problem in the meantime. Kind regards, -- Bram Schoenmakers What is mind? No matter. What is matter? Never mind. (Punch, 1855) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 'nodump' on directories: new contents still dumped
On Mon, 19 Mar 2007 12:35:25 + Alex Zbyslaw writes: Bram Schoenmakers wrote: Op vrijdag 16 maart 2007, schreef Alex Zbyslaw: Can you try explicitly putting a -h 0 into your incremental command line and see if that makes a difference? I've done that and now dump behaves like it should. I don't understand why, because the man page says that -h 1 is default (and shouldn't be supplied then). But with -h 0 on every incremental dump it's OK now. My reading of the man doesn't suggest that -h shouldn't be supplied then, ie that -h 1 is only the default *iff* you supply -h at all, not that -h 1 is default if you don't mention -h .. but I could be mistaken! I can only think of two possibilities: 1) There is a bug in whatever version of FreeBSD you are running and -h 1 is somehow *not* the default. 6.2 Release? 2) There is some kind of bug with your command line, but without seeing it, I can't tell. Glad you got the problem worked around; when I finally get around to 6.2 I will be curious to see if I can replicate the problem. Or perhaps it only requires clarification / better phrasing in the man? Cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 'nodump' on directories: new contents still dumped
Op vrijdag 16 maart 2007, schreef Alex Zbyslaw: Can you try explicitly putting a -h 0 into your incremental command line and see if that makes a difference? I've done that and now dump behaves like it should. I don't understand why, because the man page says that -h 1 is default (and shouldn't be supplied then). But with -h 0 on every incremental dump it's OK now. Thanks for the ideas. -- Bram Schoenmakers You can contact me directly with Yahoo Instant Messenger with bramschoenmakers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 'nodump' on directories: new contents still dumped
I'm using dump(8) for backing up a FreeBSD 4.10 server. In order to decrease the resulting file size, I flagged some directories like /usr/ports and /usr/src with 'nodump'. I adjusted the dump level 0 script to have -h 0, so that worked fine. The other scripts for dumps 0 do not have a -h flag set, because -h 1 is default. POSSIBLY you should but -h 0 always. but it's just a guess. The problem is that new files appearing in the /usr/ports tree (daily portsnap cron) do not have the 'nodump' flag set. But despite the 'nodump' flag on the /usr/ports directory, the new files in the tree are still dumped. at least in FreeBSD 6.2 there is no such problems. i dump my machine to tape drive using this flags and works as expected. i flag with nodump /usr/ports /usr/src/sys/i386/compile/* /tmp /var/spool/squid/* etc.. One 'hack' is to run a script prior to the dump to recursively set all 'nodump' flags where appropriate, but I'm hoping that someone can enlighten me what is going on. something isn't going up as it should. i use dump and chflags nodump and it works as expected and as manual says ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 'nodump' on directories: new contents still dumped
Bram Schoenmakers wrote: On Thursday 15 March 2007 13:57, Bram Schoenmakers wrote: I'm using dump(8) for backing up a FreeBSD 4.10 server. [...] The problem is that new files appearing in the /usr/ports tree (daily portsnap cron) do not have the 'nodump' flag set. But despite the 'nodump' flag on the /usr/ports directory, the new files in the tree are still dumped. I understood that dump does not enter directories with 'nodump' flag set, so it shouldn't see the new files inside, right? Or is this behavior implemented in a newer version than FreeBSD 4.10? I have scanned the CVS logs for dump, but couldn't find anything relevant. -h 0 just works fine, that is not the problem. I may have forgotten one detail in case that was not clear. The level 0 backup does not contain any folder marked with 'nodump' (so it's all OK, despite the -h0 you mentioned). New contents (which have no flags set) in these folders emerge in higher level dumps. The problem is that dump(8) enters directories with 'nodump' flags set while it shouldn't. I'll second what Wojciech said: I've been using nodump flags for some time and never seen the symptoms you describe. I have just verified that 5.4 does not do this for me - even with /usr/ports which I too neglect to dump! However, you are running an ancient, obsolete version (4.10). Can you try explicitly putting a -h 0 into your incremental command line and see if that makes a difference? If it still does what you describe, show us the exact command line you are using. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
'nodump' on directories: new contents still dumped
Hi, I'm using dump(8) for backing up a FreeBSD 4.10 server. In order to decrease the resulting file size, I flagged some directories like /usr/ports and /usr/src with 'nodump'. I adjusted the dump level 0 script to have -h 0, so that worked fine. The other scripts for dumps 0 do not have a -h flag set, because -h 1 is default. The problem is that new files appearing in the /usr/ports tree (daily portsnap cron) do not have the 'nodump' flag set. But despite the 'nodump' flag on the /usr/ports directory, the new files in the tree are still dumped. I understood that dump does not enter directories with 'nodump' flag set, so it shouldn't see the new files inside, right? Or is this behavior implemented in a newer version than FreeBSD 4.10? I have scanned the CVS logs for dump, but couldn't find anything relevant. One 'hack' is to run a script prior to the dump to recursively set all 'nodump' flags where appropriate, but I'm hoping that someone can enlighten me what is going on. Thanks in advance, -- Bram Schoenmakers What is mind? No matter. What is matter? Never mind. (Punch, 1855) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 'nodump' on directories: new contents still dumped
On Thursday 15 March 2007 13:57, Bram Schoenmakers wrote: I'm using dump(8) for backing up a FreeBSD 4.10 server. In order to decrease the resulting file size, I flagged some directories like /usr/ports and /usr/src with 'nodump'. I adjusted the dump level 0 script to have -h 0, so that worked fine. The other scripts for dumps 0 do not have a -h flag set, because -h 1 is default. The problem is that new files appearing in the /usr/ports tree (daily portsnap cron) do not have the 'nodump' flag set. But despite the 'nodump' flag on the /usr/ports directory, the new files in the tree are still dumped. I understood that dump does not enter directories with 'nodump' flag set, so it shouldn't see the new files inside, right? Or is this behavior implemented in a newer version than FreeBSD 4.10? I have scanned the CVS logs for dump, but couldn't find anything relevant. Read the dump manpage more carefully, and pay particular attention to the -h flag. You probably want '-h0'. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 'nodump' on directories: new contents still dumped
On Thursday 15 March 2007 14:37, John Nielsen wrote: On Thursday 15 March 2007 13:57, Bram Schoenmakers wrote: I'm using dump(8) for backing up a FreeBSD 4.10 server. In order to decrease the resulting file size, I flagged some directories like /usr/ports and /usr/src with 'nodump'. I adjusted the dump level 0 script to have -h 0, so that worked fine. The other scripts for dumps 0 do not have a -h flag set, because -h 1 is default. The problem is that new files appearing in the /usr/ports tree (daily portsnap cron) do not have the 'nodump' flag set. But despite the 'nodump' flag on the /usr/ports directory, the new files in the tree are still dumped. I understood that dump does not enter directories with 'nodump' flag set, so it shouldn't see the new files inside, right? Or is this behavior implemented in a newer version than FreeBSD 4.10? I have scanned the CVS logs for dump, but couldn't find anything relevant. Read the dump manpage more carefully, and pay particular attention to the -h flag. You probably want '-h0'. Sorry.. I obviously didn't read your post carefully enough. My understanding is the same as yours (also from versions more recent than 4.x), so I don't have any additional input. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 'nodump' on directories: new contents still dumped
Op donderdag 15 maart 2007, schreef John Nielsen: Hi, On Thursday 15 March 2007 13:57, Bram Schoenmakers wrote: I'm using dump(8) for backing up a FreeBSD 4.10 server. In order to decrease the resulting file size, I flagged some directories like /usr/ports and /usr/src with 'nodump'. I adjusted the dump level 0 script to have -h 0, so that worked fine. The other scripts for dumps 0 do not have a -h flag set, because -h 1 is default. The problem is that new files appearing in the /usr/ports tree (daily portsnap cron) do not have the 'nodump' flag set. But despite the 'nodump' flag on the /usr/ports directory, the new files in the tree are still dumped. I understood that dump does not enter directories with 'nodump' flag set, so it shouldn't see the new files inside, right? Or is this behavior implemented in a newer version than FreeBSD 4.10? I have scanned the CVS logs for dump, but couldn't find anything relevant. Read the dump manpage more carefully, and pay particular attention to the -h flag. You probably want '-h0'. -h 0 just works fine, that is not the problem. I may have forgotten one detail in case that was not clear. The level 0 backup does not contain any folder marked with 'nodump' (so it's all OK, despite the -h0 you mentioned). New contents (which have no flags set) in these folders emerge in higher level dumps. The problem is that dump(8) enters directories with 'nodump' flags set while it shouldn't. Kind regards, -- Bram Schoenmakers What is mind? No matter. What is matter? Never mind. (Punch, 1855) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
