Re: ffs issue was Re: ataraid issue was Re: [netbsd-7] Critical issue with ffs+log

2016-01-25 Thread BERTRAND Joël
Hello, I've seen that FreeBSD has the same issue : https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192490 "1. (Cause) rm -Rf is being run on a path and a subdirectory concurrently. 2. (Effect) rm -Rf is failing because fts_read isn't properly filtering out certain errors like

Re: Boot from raidframe on gpt?

2016-01-25 Thread Jonathan A. Kollasch
On Mon, Jan 25, 2016 at 06:03:34PM +, John Klos wrote: > I have: > > gpt show wd1 >startsize index contents >0 1 PMBR >1 1 Pri GPT header >2 32 Pri GPT table > 34 990 >

Boot from raidframe on gpt?

2016-01-25 Thread John Klos
I have: gpt show wd1 startsize index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 34 990 1024 7746927616 1 GPT part - NetBSD RAIDFrame component

ffs issue was Re: ataraid issue was Re: [netbsd-7] Critical issue with ffs+log

2016-01-25 Thread BERTRAND Joël
Michael van Elst a écrit : On Fri, Jan 22, 2016 at 11:03:51AM +0100, BERTRAND Joël wrote: Michael van Elst a écrit : joel.bertr...@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) writes: By dkctl wd0/1 setcache none save ? I will try next saturday. But if both disks are unsynchronized,

Re: ffs issue was Re: ataraid issue was Re: [netbsd-7] Critical issue with ffs+log

2016-01-25 Thread BERTRAND Joël
Hello, fsck on faulty fs returns : legendre# fsck -f raid0e ** /dev/rraid0e ** File system is already clean ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames UNALLOCATED I=5313299 OWNER=0 MODE=0 SIZE=0 MTIME=Jan 25 00:40 2016