On Sun, Sep 15, 2013 at 10:19:41PM +0300, Marcus Sundman wrote:
>
> It's a SanDisk SSD U100.
Here's one report of someone who had an experience with U100 in an
Asus UX31E:
https://communities.intel.com/thread/32515
> A lot. I have lsyncd running here most of the time, backing up to my
> raid-z
On 14.09.2013 05:41, Theodore Ts'o wrote:
On Thu, Sep 12, 2013 at 08:59:07PM +0300, Marcus Sundman wrote:
At 128 GB it is extremely small as it is, and I'm really struggling
to fit all on it. Most of my stuff is on my NAS (which has almost 10
TB space), but still I need several code repositories
On Thu, Sep 12, 2013 at 08:59:07PM +0300, Marcus Sundman wrote:
>
> At 128 GB it is extremely small as it is, and I'm really struggling
> to fit all on it. Most of my stuff is on my NAS (which has almost 10
> TB space), but still I need several code repositories and the
> development environment a
On Fri 13-09-13 09:35:05, Marcus Sundman wrote:
> On 12.09.2013 23:46, Jan Kara wrote:
> >On Thu 12-09-13 20:59:07, Marcus Sundman wrote:
> >>On 12.09.2013 19:35, Jan Kara wrote:
> >>>On Thu 12-09-13 18:08:13, Marcus Sundman wrote:
> And can I somehow "reset" whatever it is that is making it wo
On 12.09.2013 23:46, Jan Kara wrote:
On Thu 12-09-13 20:59:07, Marcus Sundman wrote:
On 12.09.2013 19:35, Jan Kara wrote:
On Thu 12-09-13 18:08:13, Marcus Sundman wrote:
And can I somehow "reset" whatever it is that is making it worse so
that it becomes good again? That way I could spend maybe
On Thu 12-09-13 20:59:07, Marcus Sundman wrote:
> On 12.09.2013 19:35, Jan Kara wrote:
> >On Thu 12-09-13 18:08:13, Marcus Sundman wrote:
> >>And can I somehow "reset" whatever it is that is making it worse so
> >>that it becomes good again? That way I could spend maybe 1 hour once
> >>every few mo
On 12.09.2013 19:35, Jan Kara wrote:
On Thu 12-09-13 18:08:13, Marcus Sundman wrote:
And can I somehow "reset" whatever it is that is making it worse so
that it becomes good again? That way I could spend maybe 1 hour once
every few months to get it back to top speed.
Any other ideas how I could
On Thu 12-09-13 18:08:13, Marcus Sundman wrote:
> On 12.09.2013 17:39, Jan Kara wrote:
> >On Thu 12-09-13 16:47:43, Marcus Sundman wrote:
> >>On 12.09.2013 16:10, Jan Kara wrote:
> >>> So now you run without 'discard' mount option, right? My guess then
> >>> would
> >>>be that the FTL layer on y
On 12.09.2013 17:39, Jan Kara wrote:
On Thu 12-09-13 16:47:43, Marcus Sundman wrote:
On 12.09.2013 16:10, Jan Kara wrote:
So now you run without 'discard' mount option, right? My guess then would
be that the FTL layer on your SSD is just crappy and as the erase blocks
get more fragmented as
On Thu 12-09-13 16:47:43, Marcus Sundman wrote:
> On 12.09.2013 16:10, Jan Kara wrote:
> >On Thu 12-09-13 15:57:32, Marcus Sundman wrote:
> >>On 27.02.2013 01:17, Jan Kara wrote:
> >>>On Tue 26-02-13 20:41:36, Marcus Sundman wrote:
> On 24.02.2013 03:20, Theodore Ts'o wrote:
> >On Sun, Feb
On 12.09.2013 16:10, Jan Kara wrote:
On Thu 12-09-13 15:57:32, Marcus Sundman wrote:
On 27.02.2013 01:17, Jan Kara wrote:
On Tue 26-02-13 20:41:36, Marcus Sundman wrote:
On 24.02.2013 03:20, Theodore Ts'o wrote:
On Sun, Feb 24, 2013 at 11:12:22AM +1100, Dave Chinner wrote:
/dev/sda6 /home ex
On 27.02.2013 01:17, Jan Kara wrote:
On Tue 26-02-13 20:41:36, Marcus Sundman wrote:
On 24.02.2013 03:20, Theodore Ts'o wrote:
On Sun, Feb 24, 2013 at 11:12:22AM +1100, Dave Chinner wrote:
/dev/sda6 /home ext4 rw,noatime,discard 0 0
^^^
I'd say that's y
On Thu 12-09-13 15:57:32, Marcus Sundman wrote:
> On 27.02.2013 01:17, Jan Kara wrote:
> >On Tue 26-02-13 20:41:36, Marcus Sundman wrote:
> >>On 24.02.2013 03:20, Theodore Ts'o wrote:
> >>>On Sun, Feb 24, 2013 at 11:12:22AM +1100, Dave Chinner wrote:
> >>/dev/sda6 /home ext4 rw,noatime,discard
On Tue 26-02-13 20:41:36, Marcus Sundman wrote:
> On 24.02.2013 03:20, Theodore Ts'o wrote:
> >On Sun, Feb 24, 2013 at 11:12:22AM +1100, Dave Chinner wrote:
> /dev/sda6 /home ext4 rw,noatime,discard 0 0
> >>^^^
> >>I'd say that's your problem
> >Looks
On Tue, Feb 26, 2013 at 08:41:36PM +0200, Marcus Sundman wrote:
>
> So, after reading up a bit on this trimming I'm thinking maybe my
> filesystem's block sizes don't match up with my SSD's blocks (or
> whatever its write unit is called). Then writing a FS block would
> always write to multiple SS
On 24.02.2013 03:20, Theodore Ts'o wrote:
On Sun, Feb 24, 2013 at 11:12:22AM +1100, Dave Chinner wrote:
/dev/sda6 /home ext4 rw,noatime,discard 0 0
^^^
I'd say that's your problem
Looks like the Sandisk U100 is a good SSD for me to put on my personal
On Sat 23-02-13 01:27:38, Marcus Sundman wrote:
> Sure:
> >$ cat /proc/mounts
> >rootfs / rootfs rw 0 0
> >sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
> >proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
> >udev /dev devtmpfs rw,relatime,size=1964816k,nr_inodes=491204,mode=755 0 0
> >dev
On Sun, Feb 24, 2013 at 11:12:22AM +1100, Dave Chinner wrote:
> > >/dev/sda6 /home ext4 rw,noatime,discard 0 0
>^^^
> I'd say that's your problem
Looks like the Sandisk U100 is a good SSD for me to put on my personal
"avoid" list:
http://thessdreview.co
On Sat, Feb 23, 2013 at 01:27:38AM +0200, Marcus Sundman wrote:
> >$ cat /proc/mounts
> >rootfs / rootfs rw 0 0
> >sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
> >proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
> >udev /dev devtmpfs rw,relatime,size=1964816k,nr_inodes=491204,mode=755 0
On 22.02.2013 22:51, Jan Kara wrote:
On Wed 20-02-13 13:40:03, Marcus Sundman wrote:
On 20.02.2013 10:42, Marcus Sundman wrote:
On 05.12.2012 17:32, Jan Kara wrote:
I see. Maybe you could have something like
while true; do echo w >/proc/sysrq-trigger; sleep 10; done
running in the backgr
On Wed 20-02-13 13:40:03, Marcus Sundman wrote:
> On 20.02.2013 10:42, Marcus Sundman wrote:
> >On 05.12.2012 17:32, Jan Kara wrote:
> >> I see. Maybe you could have something like
> >>while true; do echo w >/proc/sysrq-trigger; sleep 10; done
> >> running in the background?
> >
> >Sure, but I
On 20.02.2013 10:42, Marcus Sundman wrote:
On 05.12.2012 17:32, Jan Kara wrote:
I see. Maybe you could have something like
while true; do echo w >/proc/sysrq-trigger; sleep 10; done
running in the background?
Sure, but I suspect it'll take until the worst is over before it
manages to lo
On 05.12.2012 17:32, Jan Kara wrote:
On Tue 27-11-12 18:14:42, Marcus Sundman wrote:
On 22.11.2012 01:30, Jan Kara wrote:
On Fri 16-11-12 03:11:22, Marcus Sundman wrote:
On 13.11.2012 15:51, Jan Kara wrote:
On Fri 09-11-12 15:12:43, Marcus Sundman wrote:
On 09.11.2012 01:41, Marcus Sundman w
On Tue 27-11-12 18:14:42, Marcus Sundman wrote:
> On 22.11.2012 01:30, Jan Kara wrote:
> >On Fri 16-11-12 03:11:22, Marcus Sundman wrote:
> >>On 13.11.2012 15:51, Jan Kara wrote:
> >>>On Fri 09-11-12 15:12:43, Marcus Sundman wrote:
> On 09.11.2012 01:41, Marcus Sundman wrote:
> >On 07.11.20
On 22.11.2012 01:30, Jan Kara wrote:
On Fri 16-11-12 03:11:22, Marcus Sundman wrote:
On 13.11.2012 15:51, Jan Kara wrote:
On Fri 09-11-12 15:12:43, Marcus Sundman wrote:
On 09.11.2012 01:41, Marcus Sundman wrote:
On 07.11.2012 18:17, Jan Kara wrote:
On Fri 02-11-12 04:19:24, Marcus Sundman w
On Fri 16-11-12 03:11:22, Marcus Sundman wrote:
> On 13.11.2012 15:51, Jan Kara wrote:
> >On Fri 09-11-12 15:12:43, Marcus Sundman wrote:
> >>On 09.11.2012 01:41, Marcus Sundman wrote:
> >>>On 07.11.2012 18:17, Jan Kara wrote:
> On Fri 02-11-12 04:19:24, Marcus Sundman wrote:
> >Also, and t
On 13.11.2012 15:51, Jan Kara wrote:
On Fri 09-11-12 15:12:43, Marcus Sundman wrote:
On 09.11.2012 01:41, Marcus Sundman wrote:
On 07.11.2012 18:17, Jan Kara wrote:
On Fri 02-11-12 04:19:24, Marcus Sundman wrote:
Also, and this might be important, according to iotop there is
almost no disk wr
On Fri 09-11-12 15:12:43, Marcus Sundman wrote:
> On 09.11.2012 01:41, Marcus Sundman wrote:
> >On 07.11.2012 18:17, Jan Kara wrote:
> >>On Fri 02-11-12 04:19:24, Marcus Sundman wrote:
> >>>Also, and this might be important, according to iotop there is
> >>>almost no disk writing going on during th
On 09.11.2012 01:41, Marcus Sundman wrote:
On 07.11.2012 18:17, Jan Kara wrote:
On Fri 02-11-12 04:19:24, Marcus Sundman wrote:
Also, and this might be important, according to iotop there is
almost no disk writing going on during the freeze. (Occasionally
there are a few MB/s, but mostly it's 0
On 07.11.2012 18:17, Jan Kara wrote:
On Fri 02-11-12 04:19:24, Marcus Sundman wrote:
On 01.11.2012 21:01, Jan Kara wrote:
On Mon 29-10-12 00:39:46, Marcus Sundman wrote:
Hello,
I have a big problem with the system freezing and would appreciate
any help on debugging this and pinpointing whe
On Fri 02-11-12 04:19:24, Marcus Sundman wrote:
> On 01.11.2012 21:01, Jan Kara wrote:
> >On Mon 29-10-12 00:39:46, Marcus Sundman wrote:
> > Hello,
> >
> >>I have a big problem with the system freezing and would appreciate
> >>any help on debugging this and pinpointing where exactly the problem
On 01.11.2012 21:01, Jan Kara wrote:
On Mon 29-10-12 00:39:46, Marcus Sundman wrote:
Hello,
I have a big problem with the system freezing and would appreciate
any help on debugging this and pinpointing where exactly the problem
is, so it could be fixed.
So, whenever I write to the disk the
On Mon 29-10-12 00:39:46, Marcus Sundman wrote:
Hello,
> I have a big problem with the system freezing and would appreciate
> any help on debugging this and pinpointing where exactly the problem
> is, so it could be fixed.
>
> So, whenever I write to the disk the system comes to a crawl or
> fr
Hi,
I have a big problem with the system freezing and would appreciate any
help on debugging this and pinpointing where exactly the problem is, so
it could be fixed.
So, whenever I write to the disk the system comes to a crawl or freezes
altogether. This happens even when the writing process
34 matches
Mail list logo
