Re: Does bg fsck have problems with large filesystems?
Hello, He also has a login on the machine for testing but it's turned off at the moment I'll turn it on again if he asks. I've already sent him a mail. BTW, is a simple login (I mean, for example ssh) enough for this task? I would think at least a serial console access is needed... --[ Free Software ISOs - http://www.fsn.hu/?f=download ]-- Attila Nagy e-mail: [EMAIL PROTECTED] Free Software Network (FSN.HU)phone @work: +361 210 1415 (194) cell.: +3630 306 6758 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
On Tue, 11 Feb 2003, Attila Nagy wrote: Hello, He also has a login on the machine for testing but it's turned off at the moment I'll turn it on again if he asks. I've already sent him a mail. BTW, is a simple login (I mean, for example ssh) enough for this task? I would think at least a serial console access is needed... It's 10 minutes drive away from his place :-) --[ Free Software ISOs - http://www.fsn.hu/?f=download ]-- Attila Nagy e-mail: [EMAIL PROTECTED] Free Software Network (FSN.HU) phone @work: +361 210 1415 (194) cell.: +3630 306 6758 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
Hello, I'll try to reproduce the thing on my machine as soon as possible. Perhaps it was just because it was Monday, who knows... Meanwhile I found out that my problem is 100% reproducible. Since then, I contacted Kirk McKusick, who told me that he will investigate this issue. I also gave him access to our machine, which has a 1.2 TB filesystem on it. I hope he can get in before I have to take that machine into production :) --[ Free Software ISOs - http://www.fsn.hu/?f=download ]-- Attila Nagy e-mail: [EMAIL PROTECTED] Free Software Network (FSN.HU)phone @work: +361 210 1415 (194) cell.: +3630 306 6758 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
On Mon, 10 Feb 2003, Attila Nagy wrote: Hello, I'll try to reproduce the thing on my machine as soon as possible. Perhaps it was just because it was Monday, who knows... Meanwhile I found out that my problem is 100% reproducible. Since then, I contacted Kirk McKusick, who told me that he will investigate this issue. I also gave him access to our machine, which has a 1.2 TB filesystem on it. I have a 1.9TB FS about 4 km from him.. I hope he can get in before I have to take that machine into production :) --[ Free Software ISOs - http://www.fsn.hu/?f=download ]-- Attila Nagy e-mail: [EMAIL PROTECTED] Free Software Network (FSN.HU) phone @work: +361 210 1415 (194) cell.: +3630 306 6758 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
Hello, I also gave him access to our machine, which has a 1.2 TB filesystem on it. I have a 1.9TB FS about 4 km from him.. That's great! Could you please contact him? (do you also have this problem, BTW?) Thanks, --[ Free Software ISOs - http://www.fsn.hu/?f=download ]-- Attila Nagy e-mail: [EMAIL PROTECTED] Free Software Network (FSN.HU)phone @work: +361 210 1415 (194) cell.: +3630 306 6758 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
On Mon, 10 Feb 2003, Attila Nagy wrote: Hello, I also gave him access to our machine, which has a 1.2 TB filesystem on it. I have a 1.9TB FS about 4 km from him.. That's great! Could you please contact him? (do you also have this problem, BTW?) He also has a login on the machine for testing but it's turned off at the moment I'll turn it on again if he asks. Thanks, --[ Free Software ISOs - http://www.fsn.hu/?f=download ]-- Attila Nagy e-mail: [EMAIL PROTECTED] Free Software Network (FSN.HU) phone @work: +361 210 1415 (194) cell.: +3630 306 6758 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
On Tue, Jan 28, 2003 at 06:31:42PM +0100, Gerrit Kühn wrote: I've been trying to reproduce this bug on my desktop. This machine has 2 80gb disks, one of which is dedicated with one slice. So far, after 8 hard resets, I haven't had any problem with either the machine or bgfsck hanging. I'll try to reproduce the thing on my machine as soon as possible. Perhaps it was just because it was Monday, who knows... Meanwhile I found out that my problem is 100% reproducible. My file systems look like this: Filesystem 1K-blocksUsedAvail Capacity Mounted on /dev/ad0s1a257838 67338 16987428%/ devfs 1 10 100%/dev /dev/ad0s1g 57467672 2 52870258 0%/export /dev/ad0s1f 4125838 4 3795768 0%/tmp /dev/ad0s1e 12383502 1336152 1005667012%/usr /dev/ad0s1d 41258383458 3792314 0%/var When booting with non-clean filesystems, bgfsck runs quickly over a, d, e and f. However, on g it keeps running forever. I can't kill the fsck processes and I can't access g, though the rest of the system seems to be usable as usual. Here is the output of ps axl: UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 0 0 0 0 -16 0 0 12 sched DLs ??0:00.00 (swapper) 0 1 0 0 8 0 712 392 wait ILs ??0:00.01 /sbin/init - 0 2 0 0 -8 0 0 12 g_even DL??0:00.02 (g_event) 0 3 0 0 -8 0 0 12 g_up DL??0:00.09 (g_up) 0 4 0 0 -8 0 0 12 g_down DL??0:00.19 (g_down) 0 5 0 0 -84 0 0 12 actask IL??0:00.00 (acpi_task0 0 6 0 0 -84 0 0 12 actask IL??0:00.00 (acpi_task1 0 7 0 0 -84 0 0 12 actask IL??0:00.00 (acpi_task2 0 8 0 0 -16 0 0 12 psleep DL??0:00.00 (pagedaemon 0 9 0 0 20 0 0 12 psleep DL??0:00.00 (vmdaemon) 010 0 0 -16 0 0 12 ktrace DL??0:00.00 (ktrace) 011 0 110 -16 0 0 12 - RL??2:20.07 (idle) 012 0 0 -48 0 0 12 - WL??0:00.12 (swi6: tty: 014 0 0 -44 0 0 12 - WL??0:00.00 (swi1: net) 015 0 0 76 0 0 12 sleep DL??0:00.05 (random) 019 0 0 -28 0 0 12 - WL??0:00.00 (swi5: acpi 022 0 0 -64 0 0 12 - WL??0:00.28 (irq14: ata 024 0 0 -68 0 0 12 - WL??0:00.00 (irq11: rl0 025 0 0 8 0 0 12 usbevt DL??0:00.00 (usb0) 026 0 0 8 0 0 12 usbtsk DL??0:00.00 (usbtask) 027 0 0 8 0 0 12 usbevt DL??0:00.00 (usb1) 028 0 5 -68 0 0 12 - WL??0:00.00 (irq12: fwo 029 0 0 -64 0 0 12 - WL??0:00.00 (irq6: fdc0 032 0 0 -60 0 0 12 - WL??0:00.00 (irq7: ppc0 033 0 0 -60 0 0 12 - WL??0:00.02 (irq1: atkb 036 0 34 171 0 0 12 pgzero DL??0:00.47 (pagezero) 037 0 2 -4 0 0 12 snaplk DL??0:00.24 (bufdaemon) 038 0 0 20 0 0 12 syncer DL??0:00.01 (syncer) 039 0 0 -4 0 0 12 vlruwt DL??0:00.00 (vnlru) 040 0 0 8 0 0 12 nfsidl IL??0:00.00 (nfsiod 0) 041 0 0 8 0 0 12 nfsidl IL??0:00.00 (nfsiod 1) 042 0 0 8 0 0 12 nfsidl IL??0:00.00 (nfsiod 2) 043 0 0 8 0 0 12 nfsidl IL??0:00.00 (nfsiod 3) 0 246 1 0 96 0 1172 736 select Ss??0:00.03 /usr/sbin/sy 0 267 1 0 96 0 1372 1016 select Ss??0:00.03 /usr/sbin/rp 0 350 1 155 115 0 1220 992 select Is??0:00.01 /usr/sbin/mo 0 353 1 112 110 0 1168 876 select Is??0:00.13 nfsd: master 0 355 353 155 4 0 1128 748 nfsd I ??0:00.00 nfsd: server 0 356 353 155 4 0 1128 748 nfsd I ??0:00.00 nfsd: server 0 357 353 155 4 0 1128 748 nfsd I ??0:00.00 nfsd: server 0 358 353 155 4 0 1128 748 nfsd I ??0:00.00 nfsd: server 0 374 1 0 96 0 1144 680 select Ss??0:00.00 /usr/sbin/us 0 394 1 154 115 0 1196 808 select Is??0:00.01 /usr/sbin/lp 0 454 1 153 115 0 3092 2200 select Is??0:00.63 /usr/sbin/ss 0 460 1 0 96 0 3092 2544 select Ss??0:00.01 sendmail: ac 25 463 1 153 20 0 2992 2500 pause Is??0:00.00 sendmail: Qu 0 512 1 0 8 0 1236 956 nanslp Ss??0:00.01 /usr/sbin/cr 0 522 1 0 8 0 1532 1236
Re: Does bg fsck have problems with large filesystems?
In message [EMAIL PROTECTED], Gerrit =?iso-8859-1?Q? K=FChn?= writes: On Tue, Jan 28, 2003 at 06:31:42PM +0100, Gerrit Kühn wrote: I've been trying to reproduce this bug on my desktop. This machine has 2 80gb disks, one of which is dedicated with one slice. So far, after 8 hard resets, I haven't had any problem with either the machine or bgfsck hanging. I'll try to reproduce the thing on my machine as soon as possible. Perhaps it was just because it was Monday, who knows... Meanwhile I found out that my problem is 100% reproducible. Sounds like bgfsck gets stuck in the snapshot creation. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
Just try to fsck 1.2 TB and you will be very-very patient :) Very patient indeed. I've got a 1.0TB partition about 51% full. It's still a 4-STABLE system and the last fsck from a crash last Friday (bad IBM, bad, no soup for you) took just about 55 minutes to fsck. *ugh* I'm torture testing on a 600GB partition and I was hoping to maybe roll to 5.x around March. It's probably a good thing that I didn't jump on it right away :-) Cheers, Ryan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
Dropping the number of inodes really helps fsck time; what does df -i /bigfilesystem print? fs# df -i /users Filesystem 1K-blocks Used Avail Capacity iusedifree %iused Mounted on /dev/da2s1e 999089944 457994296 46116845650% 6094282 25170996 19% /users fsize = 8192, bsize = 65536, cpg = 1421 Cheers, Ryan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
In the last episode (Jan 30), Ryan Dooley said: Just try to fsck 1.2 TB and you will be very-very patient :) Very patient indeed. I've got a 1.0TB partition about 51% full. It's still a 4-STABLE system and the last fsck from a crash last Friday (bad IBM, bad, no soup for you) took just about 55 minutes to fsck. *ugh* Dropping the number of inodes really helps fsck time; what does df -i /bigfilesystem print? I'm torture testing on a 600GB partition and I was hoping to maybe roll to 5.x around March. It's probably a good thing that I didn't jump on it right away :-) -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
Hello, I've just installed my first 5.0-rel system and did some torture-testing. When resetting the machine to test the backgrounded fsck I experienced the following problem: All filesystems came back quickly and bg fsck worked fine, except for one. I had created a large (50GB) /export filesystem on with fsck reproducively hang. See PR kern/47105. Although it speaks of much larger filesystems, than your, the problem is there. I've already written to Kirk McKusick, but it seems that he has a lot of work, because I didn't get answer. If anybody wants to look into this problem, I can give access to the machine (even serial console)... --[ Free Software ISOs - http://www.fsn.hu/?f=download ]-- Attila Nagy e-mail: [EMAIL PROTECTED] Free Software Network (FSN.HU)phone @work: +361 210 1415 (194) cell.: +3630 306 6758 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
On Tue, Jan 28, 2003 at 11:44:03AM +0100, Attila Nagy [EMAIL PROTECTED] wrote: I've just installed my first 5.0-rel system and did some torture-testing. When resetting the machine to test the backgrounded fsck I experienced the following problem: All filesystems came back quickly and bg fsck worked fine, except for one. I had created a large (50GB) /export filesystem on with fsck reproducively hang. See PR kern/47105. Although it speaks of much larger filesystems, than your, the problem is there. I've already written to Kirk McKusick, but it seems that he has a lot of work, because I didn't get answer. If anybody wants to look into this problem, I can give access to the machine (even serial console)... I don't see it listed in 5.0-RELEASE ERRATA. Several people have now reported problems with background fsck and in the case Kirk as original author is loaded with other work I see no justification to not mention the brokenness of bgfsck. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
On Tue, Jan 28, 2003 at 11:44:03AM +0100, Attila Nagy wrote: I've just installed my first 5.0-rel system and did some torture-testing. When resetting the machine to test the backgrounded fsck I experienced the following problem: All filesystems came back quickly and bg fsck worked fine, except for one. I had created a large (50GB) /export filesystem on with fsck reproducively hang. See PR kern/47105. Although it speaks of much larger filesystems, than your, the problem is there. 47105 seems to be slightly different from what I saw, because my machine never paniced; the fsck just hung forever. I've already written to Kirk McKusick, but it seems that he has a lot of work, because I didn't get answer. Ok, then things are already on their way, I guess. If anybody wants to look into this problem, I can give access to the machine (even serial console)... I wonder if it's only the large filesystem that triggers this problem. Actually I think that my 50GB are not /that/ large, and someone else should have noticed the problem before. BTW: As mentioned in the PR one workaround is to turn off bg fsck. On the other hand bg fsck is working fine on smaller filesystems. Is there a way to turn bg fsck off for just one partition? cu Gerrit -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
Hello, 47105 seems to be slightly different from what I saw, because my machine never paniced; the fsck just hung forever. It depends. My machine hangs, there's no panic. I've already written to Kirk McKusick, but it seems that he has a lot of work, because I didn't get answer. Ok, then things are already on their way, I guess. Don't know, but I hope :) I wonder if it's only the large filesystem that triggers this problem. Actually I think that my 50GB are not /that/ large, and someone else should have noticed the problem before. I wonder what's the common in our case, then. BTW: As mentioned in the PR one workaround is to turn off bg fsck. On the other hand bg fsck is working fine on smaller filesystems. Is there a way to turn bg fsck off for just one partition? I don't know any. BTW, the big partitions are those which needs the extra time, so it is very likely that you won't benefit too much from this... --[ Free Software ISOs - http://www.fsn.hu/?f=download ]-- Attila Nagy e-mail: [EMAIL PROTECTED] Free Software Network (FSN.HU)phone @work: +361 210 1415 (194) cell.: +3630 306 6758 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
On Tue, 28 Jan 2003, Vallo Kallaste wrote: On Tue, Jan 28, 2003 at 11:44:03AM +0100, Attila Nagy [EMAIL PROTECTED] wrote: I've just installed my first 5.0-rel system and did some torture-testing. When resetting the machine to test the backgrounded fsck I experienced the following problem: All filesystems came back quickly and bg fsck worked fine, except for one. I had created a large (50GB) /export filesystem on with fsck reproducively hang. See PR kern/47105. Although it speaks of much larger filesystems, than your, the problem is there. I've already written to Kirk McKusick, but it seems that he has a lot of work, because I didn't get answer. I don't see it listed in 5.0-RELEASE ERRATA. Several people have now reported problems with background fsck and in the case Kirk as original author is loaded with other work I see no justification to not mention the brokenness of bgfsck. I've been trying to reproduce this bug on my desktop. This machine has 2 80gb disks, one of which is dedicated with one slice. So far, after 8 hard resets, I haven't had any problem with either the machine or bgfsck hanging. Here's what df's output looks like: Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/ad0s1a128990834083526470%/ devfs 110 100%/dev /dev/ad0s1f257998 404 236956 0%/tmp /dev/ad0s1g 74757832 5774972 63002234 8%/usr /dev/ad0s1e25799821122 216238 9%/var procfs 440 100%/proc /dev/ad1s1e 76955976 49105248 2169425069%/export Regards, Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
On Tue, 28 Jan 2003, Andre Guibert de Bruet wrote: I don't see it listed in 5.0-RELEASE ERRATA. Several people have now reported problems with background fsck and in the case Kirk as original author is loaded with other work I see no justification to not mention the brokenness of bgfsck. I've been trying to reproduce this bug on my desktop. This machine has 2 80gb disks, one of which is dedicated with one slice. So far, after 8 hard resets, I haven't had any problem with either the machine or bgfsck hanging. Here's what df's output looks like: Following reports of problems with bgfsck during the 5.0-RC series, and prior to the release, I spent some time adding hard disks to machines, resetting without clean shutdowns, and then interrupting background fscks, piles of builds going, etc. When I started, it was fairly problematic, but after Kirk's last batch of buffer fixes, etc, it was pretty much 100% reliable on the boxes I was testing on. However, all those boxes used 40gb drives or smaller. I'll see if I can't dig up some larger drives in the next week or two and try doing that again. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
On Tue, Jan 28, 2003 at 12:22:10PM -0500, Andre Guibert de Bruet wrote: I've been trying to reproduce this bug on my desktop. This machine has 2 80gb disks, one of which is dedicated with one slice. So far, after 8 hard resets, I haven't had any problem with either the machine or bgfsck hanging. I'll try to reproduce the thing on my machine as soon as possible. Perhaps it was just because it was Monday, who knows... cu Gerrit -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
On Tue, Jan 28, 2003 at 04:23:08PM +0100, Attila Nagy wrote: 47105 seems to be slightly different from what I saw, because my machine never paniced; the fsck just hung forever. It depends. My machine hangs, there's no panic. Yes, I overlooked that in the PR when I read it first. Mine was still usable: I could switch VTs and even log in, but I couldn't do anything about the hanging fsck processes. I've already written to Kirk McKusick, but it seems that he has a lot of work, because I didn't get answer. Ok, then things are already on their way, I guess. Don't know, but I hope :) That makes two of us. :) I wonder if it's only the large filesystem that triggers this problem. Actually I think that my 50GB are not /that/ large, and someone else should have noticed the problem before. I wonder what's the common in our case, then. I really don't know. I have a SV25 barebone system from Shuttle (VIA Twister Chipset) and an IBM deskstar 80GB IDE HD. Does that sound familiar to you? BTW: As mentioned in the PR one workaround is to turn off bg fsck. On the other hand bg fsck is working fine on smaller filesystems. Is there a way to turn bg fsck off for just one partition? I don't know any. BTW, the big partitions are those which needs the extra time, so it is very likely that you won't benefit too much from this... Well, the drive has 80GB, the big partition is 50GB, so I would save something like 3/8 of the time. Not too much, but better than nothing, I thought. ;) cu Gerrit -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
On Tue, Jan 28, 2003 at 12:34:25PM -0500, Robert Watson wrote: Following reports of problems with bgfsck during the 5.0-RC series, and prior to the release, I spent some time adding hard disks to machines, resetting without clean shutdowns, and then interrupting background fscks, piles of builds going, etc. When I started, it was fairly problematic, but after Kirk's last batch of buffer fixes, etc, it was pretty much 100% reliable on the boxes I was testing on. Have these fixes been applied to 5.0-rel, too? If not, I'm considering updating to -current. cu Gerrit -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
Hello, I really don't know. I have a SV25 barebone system from Shuttle (VIA Twister Chipset) and an IBM deskstar 80GB IDE HD. Does that sound familiar to you? Nope, mine is completely different. It is a HP tc4100 (I think it has an Intel MOBO, but I'm not sure) with an AHA-2940 controller and a Promise RM-8000 attached to it with 8 pieces of WD-2000JB disks. Well, the drive has 80GB, the big partition is 50GB, so I would save something like 3/8 of the time. Not too much, but better than nothing, I thought. ;) Just try to fsck 1.2 TB and you will be very-very patient :) --[ Free Software ISOs - http://www.fsn.hu/?f=download ]-- Attila Nagy e-mail: [EMAIL PROTECTED] Free Software Network (FSN.HU)phone @work: +361 210 1415 (194) cell.: +3630 306 6758 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Does bg fsck have problems with large filesystems?
On Tue, 28 Jan 2003, Gerrit Kühn wrote: On Tue, Jan 28, 2003 at 12:34:25PM -0500, Robert Watson wrote: Following reports of problems with bgfsck during the 5.0-RC series, and prior to the release, I spent some time adding hard disks to machines, resetting without clean shutdowns, and then interrupting background fscks, piles of builds going, etc. When I started, it was fairly problematic, but after Kirk's last batch of buffer fixes, etc, it was pretty much 100% reliable on the boxes I was testing on. Have these fixes been applied to 5.0-rel, too? If not, I'm considering updating to -current. I believe all of the fixes were applied prior to the release, and that they were all merged into the release branch, and hence should be present in the final cut of 5.0. The bugfixes were largely in the area of snapshot handling, and so can be picked out of the CVS logs largely on the file ffs_snapshot.c. Most were for resource or locking deadlock issues. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Does bg fsck have problems with large filesystems?
Hi all, I've just installed my first 5.0-rel system and did some torture-testing. When resetting the machine to test the backgrounded fsck I experienced the following problem: All filesystems came back quickly and bg fsck worked fine, except for one. I had created a large (50GB) /export filesystem on with fsck reproducively hang. I also couldn't reboot the system cleanly anymore, because of those fsck processes not going away. Finally, I commented out /export from /etc/fstab and run fsck manually in fg mode after the rest of the system had been checked cleanly. There were a few errors, and after that the check finished and marked the system as clean. However, mounting the clean system took several seconds and gave me this message from the kernel: FFS_SNAPSHOT_MOUNT: old format snapshot inode 4 Well, whatever... :) Nevertheless everything is working fine now, again. I havn't checked yet, but will this happen every time my systems reboots without unmounting the filesystems cleanly? Is anything wrong with filesystems that large, or could I have done anything else that causes this strange behaviour? cu Gerrit -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
